Joplin: [Feature Request] Mark syntax

Created on 25 Apr 2018  ·  8Comments  ·  Source: laurent22/joplin

I'd like to use the Markdown "highlight"/"mark" syntax, ==like this==.

Sample implementation e.g. here: https://github.com/markdown-it/markdown-it-mark

I can use the <mark> tag instead (and that works well within Joplin), but I'd appreciate having a shorthand syntax instead.

enhancement stale

Most helpful comment

This was fixed in #1347 by the addition of the markdown-it-mark plugin.

All 8 comments

Is it a standard Markdown feature?

At this point, I honestly don't know what to consider "standard", when it comes to markdown. I've seen it plenty of times and it's really quite handy. And there's that markdown-it plugin, so it should be relatively simple to support. Beyond that, 🤷🏻‍♀️.

I was just searching on what is typical for highlighting the text in Markdown. Seems there is no defined standards, but most applications I found have used ==text== to highlight the text. I also found <mark> in stackoverflow which works in Joplin but:

  1. the text would be highlighted in a dark red color
  2. the´codes´ would become unreadable due to gray background and white text color

It would be nice to have it as normal yellow color. (seems the markdown-it already have the yellow background color with black text with the same == syntax)

Also I would like to suggest that user be able to highlight the text while being in preview layout by selecting the text, rightclick and select highlight from the rightclick menu. (would be very convenient when reading the text

I was checking for this feature. Recently I moved from evernote and a lot of my marks in evernote are not available in joplin, searching I found <mark> and it worked as expected.

Checking the enex file, evernote mark those highlights as

<span style="x-evernote:highlighted;background-color:#F6EE96;">

This was fixed in #1347 by the addition of the markdown-it-mark plugin.

w00t! Thank you @CalebJohn . Confirmed highlights work great!

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "backlog" and I will leave it open. Thank you for your contributions.

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.

Was this page helpful?
0 / 5 - 0 ratings