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
I have to think someone else has experienced this but in any case. I need to use the standard Markdown syntax of "==" for highlighting. If I leave the default in the plug in then that gets interpreted as a cloze. The rendering is nice cause it has color but it's not just a highlight now. If you use the curly brackets then when you look at the Reader or Live Preview you are forced to see them in your text, ugly! There has to be a happy medium here, has to be! Thinking outside the box here but why not "hide" the brackets in preview or better yet change the "==" to be something like "=" and "=".
Any advice or suggestions is greatly appreciated. Thanks
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have to think someone else has experienced this but in any case. I need to use the standard Markdown syntax of "==" for highlighting. If I leave the default in the plug in then that gets interpreted as a cloze. The rendering is nice cause it has color but it's not just a highlight now. If you use the curly brackets then when you look at the Reader or Live Preview you are forced to see them in your text, ugly! There has to be a happy medium here, has to be! Thinking outside the box here but why not "hide" the brackets in preview or better yet change the "==" to be something like "=" and "=".
Any advice or suggestions is greatly appreciated. Thanks
Beta Was this translation helpful? Give feedback.
All reactions