You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The problem with the cloze trigger (==) ist that, it is used in standard markdown to highlight text.
So it is not possible to "highlight" text in a note which has a cards-deck set, because all these highlights get recognized as clozes.
Describe the solution you'd like
I would be great if the trigger symbols/string could be customized. I know this is probably not a small change to the codebase. An alternative would be to disable the == trigger (because there is the {} as a second one) or change it to maybe === (tree equal symbols).
Thank you very much, I love this plugin and my vault would not be as powerful without it.
PS.: for the people with the same problem as me:
as a workaround, I currently use the plugin Highligthr which formats the selected text to an HTML styled "highlight"
The text was updated successfully, but these errors were encountered:
+1. Furthermore, == also sometimes causes problems if it appears inside inline code blocks (which, since it is the equality comparison operator in many programming languages, is not uncommon in my experience).
(Currently, a workaround for this is to add a zero-width space character () between the two equality signs: ==.)
+1 also from my side. I've started to use the plugin a week ago and really like it.
Today I started to create Anki cards for a note with several highlighted sentences and after there were now clozed deletion cards in the Anki deck I was looking for an option to disable this feature.
Is your feature request related to a problem? Please describe.
The problem with the cloze trigger (
==
) ist that, it is used in standard markdown to highlight text.So it is not possible to "highlight" text in a note which has a cards-deck set, because all these highlights get recognized as clozes.
Describe the solution you'd like
I would be great if the trigger symbols/string could be customized. I know this is probably not a small change to the codebase. An alternative would be to disable the
==
trigger (because there is the{}
as a second one) or change it to maybe===
(tree equal symbols).Thank you very much, I love this plugin and my vault would not be as powerful without it.
PS.: for the people with the same problem as me:
as a workaround, I currently use the plugin Highligthr which formats the selected text to an HTML styled "highlight"
The text was updated successfully, but these errors were encountered: