Plugin: Rich Markdown

CalebJohn · 2024-05-17T18:29:18.576Z

Thank you for the reports @nonobio, I don't have time to fix them right away but I've tracked them on github so they don't get lost.

github.com/CalebJohn/joplin-rich-markdown

Checkboxes actions of the context menu are not displayed if the last line of the selection does not contain a checkbox

opened 06:25PM - 17 May 24 UTC

CalebJohn

bug

This is because the current code uses the location of the cursor to determine th…e items to add to the context menu. This needs to be fixed for multiline selections, so that the correct prompt is present. ![image](https://github.com/CalebJohn/joplin-rich-markdown/assets/2179547/bc1fa6d5-4055-45d8-a92c-7a6e6361df15) [source: nonobio on discourse](https://discourse.joplinapp.org/t/plugin-rich-markdown/15053/369?u=calebjohn)

github.com/CalebJohn/joplin-rich-markdown

Internal links with checkboxes in the title cannot be clicked

opened 06:27PM - 17 May 24 UTC

CalebJohn

bug

This is likely caused by an overly greedy checkbox regex which is hijacking the …section. ![image](https://github.com/CalebJohn/joplin-rich-markdown/assets/2179547/85e95002-2f2c-466f-b2c9-77638bfea919) [source: nonobio on discourse](https://discourse.joplinapp.org/t/plugin-rich-markdown/15053/369?u=calebjohn)

And as for anchor links not scrolling to the right place, that is indeed a limitation of the current version, it is high priority for me to fix.

github.com/CalebJohn/joplin-rich-markdown

Support scrolling to footers and anchor links

opened 05:40PM - 29 Oct 23 UTC

CalebJohn

[ref](https://discourse.joplinapp.org/t/plugin-rich-markdown/15053/349)

nonobio · 2024-05-18T05:56:38.132Z

Thanks

CalebJohn:

And as for anchor links not scrolling to the right place, that is indeed a limitation of the current version, it is high priority for me to fix.

Are you talking about the current version of Rich Markdown or Joplin?
Because for me the problem is present even without any plugin installed (without Rich Markdown).

There are two things I notice:

Sometimes the note is not positioned at all in the right place, whether in the editor or the renderer.
Sometimes it is positioned well in the renderer but not in the editor (this is where I have to move the text up or down on the renderer side so that the editor aligns it).

CalebJohn · 2024-05-19T18:30:53.274Z

I was talking about rich markdown, but I see now that you're talking about a different issue. You should report it on the Joplin issue tracker.

GitHub

Issues · laurent22/joplin

Joplin - the secure note taking and to-do app with synchronisation capabilities for Windows, macOS, Linux, Android and iOS. - Issues · laurent22/joplin

nonobio · 2024-05-20T09:42:04.682Z

Thanks, it's done:

github.com/laurent22/joplin

Anchor links works only in renderer and not everytime

opened 09:39AM - 20 May 24 UTC

nonobio

bug

### Operating system Windows ### Joplin version 3.0.6 ### Desktop ve…rsion info Joplin 3.0.6 (prod, win32) ID client : 1442e227e6af42d19aa8f41041c138ef Version de Synchro : 3 Version du profil : 47 Trousseau supporté : Oui Révision : 18b9f5c Backup: 1.4.1 Note overview: 1.7.1 Note Tabs: 1.4.0 Outline: 1.5.13 Rich Markdown: 0.15.0 Search & Replace: 2.2.0 ### Current behaviour Hi, When I click on an anchor link of another note, Joplin goes to the other note but sometimes positions itself at the beginning of the note (I seem to see the right section briefly). Moreover, even when it works, it is only in the renderer panel and not in the editor. To put the editor in the right place, I have to move the text up or down in the viewer. ![20240429 Joplin liens anchor fonctionnent mal et seulement dans rendu](https://github.com/laurent22/joplin/assets/7425799/6f76c1a0-511b-40cf-9514-a2c23bffe156) I tried deactivating all my plugins, but the problem is still present. Thanks ### Expected behaviour The renderer and editor should be positioned in the right place ### Llinks Topic on forum: https://discourse.joplinapp.org/t/anchor-links-works-only-in-renderer-and-not-everytime/38137

nickzeff · 2024-05-24T03:16:27.608Z

Hey @CalebJohn ... sorry for being cheeky, but thought I would try my luck again...

Do you think any chance of implementing PDF preview being displayed inline in the markdown editor, especially since v3 has now added support for loading PDFs with imaging API.

I am fine for you to give the same answer as last time, but thought I would forward this new info

github.com/laurent22/joplin

Desktop: Resolves #9794: Plugin API: Add support for loading PDFs with the imaging API

laurent22:dev ← personalizedrefrigerator:pr/plugin-api/pdf-to-image-api

opened 04:37PM - 21 Mar 24 UTC

personalizedrefrigerator

+303 -75

# Summary Resolves #9794. Adds a plugin API to convert PDFs to images. …Specifically, it adds the following: - `joplin.imaging.createFromPdfResource` - `joplin.imaging.createFromPdfPath`: Creates images from a PDF file (one per page). Returns a handle to each page. It also makes the following changes to existing methods: - `joplin.imaging.createFromResource` and `joplin.imaging.createFromPath`: If given a path to a pdf resource or file (based on the file extension), return an image of its first page. - `joplin.imaging.free`: Support freeing an array of image handles. # Testing This pull request updates the `imaging` example plugin to use the new APIs. To manually test this pull request using that plugin, 1. Open a note that contains a PDF link in the markdown editor. 2. Select the PDF link. 3. Click on the second gear icon in the toolbar. 4. Verify that images for the first 10 pages are inserted into the note.

shikuz · 2024-05-25T12:58:05.659Z

Wanted to share some RM CSS tricks. Each one is made up of two parts:

JSON to be pasted into the settings at Rich Markdown --> Advanced Settings --> Custom classes JSON. This creates new CSS classes out of text patterns.
CSS to be pasted into Joplin's userchrome.css (AKA Appearance --> Custom stylesheet for Joplin-wide app styles).

Highlight tags in the editor

Preview:

image1072×116 18.6 KB

JSON:

[{ "name": "rm-tag", "regex": "(?<=^|\\s)([#@+]|\\/\\/)([^\\s#@+]*\\w)" }]

CSS:

div.CodeMirror span.cm-rm-tag {
    background-color: #7698b3;
    color: white !important;
    padding: 0em 2px;
    border-radius: 5px;
    display: inline;
}

Colour-coded checkboxes in the editor

Preview:

These [x]it!-inspired checkbox styles represent various possible states of tasks. (See also this plugin, which renders these checkboxes in a panel.)

JSON:

[{
	"name": "rm-xitOpen",
	"regex": "(?<=^\\s*)[-+*] \\[ \\](?=\\s.*)"
},
{
	"name": "rm-xitDone",
	"regex": "(?<=^\\s*)[-+*] \\[x\\](?=\\s.*)"
},
{
	"name": "rm-xitOngoing",
	"regex": "(?<=^\\s*)[-+*] \\[@\\](?=\\s.*)"
},
{
	"name": "rm-xitObsolete",
	"regex": "(?<=^\\s*)[-+*] \\[~\\](?=\\s.*)"
},
{
	"name": "rm-xitInQuestion",
	"regex": "(?<=^\\s*)[-+*] \\[\\?\\](?=\\s.*)"
},
{
	"name": "rm-xitBlocked",
	"regex": "(?<=^\\s*)[-+*] \\[!\\](?=\\s.*)"
}]

CSS:

I included an extra commented line in each class for optionally highlighting the checkbox.

div.CodeMirror .cm-rm-xitOpen { /* Add * after the class for CM6 */
    font-family: monospace !important;
    color: #4178be !important;
    font-weight: bold !important;
    /* background-color: #a3c3f5 !important; */
}

div.CodeMirror .cm-rm-xitDone { /* Add * after the class for CM6 */
    font-family: monospace !important;
    color: #64a073 !important;
    font-weight: bold !important;
    /* background-color: #b9d7bf !important; */
}

div.CodeMirror .cm-rm-xitOngoing { /* Add * after the class for CM6 */
    font-family: monospace !important;
    color: #cb55c2 !important;
    font-weight: bold !important;
    /* background-color: #ebace8 !important; */
}

div.CodeMirror .cm-rm-xitObsolete { /* Add * after the class for CM6 */
    font-family: monospace !important;
    color: #999999 !important;
    font-weight: bold !important;
    /* background-color: #c4c4c4 !important; */
}

div.CodeMirror .cm-rm-xitInQuestion { /* Add * after the class for CM6 */
    font-family: monospace !important;
    color: #cc913f !important;
    font-weight: bold !important;
    /* background-color: #e9c79f !important; */
}

div.CodeMirror .cm-rm-xitBlocked { /* Add * after the class for CM6 */
    font-family: monospace !important;
    color: #e22d2d !important;
    font-weight: bold !important;
    /* background-color: #f5aaaa !important; */
}

restreachi · 2024-06-07T23:48:29.298Z

Does anybody know if this plugin is known to be safe privacy-wise? Their latest version 15.0.0 doesn't seem to be on Github...

CalebJohn · 2024-06-08T00:06:33.950Z

v0.15.0 is on github, I just didn't bother manually creating a github "release" for it. I just pressed the release button so it should be safe now

Lombra · 2024-07-09T18:21:39.540Z

Hi,

Is this plugin supported in version 3.x? I just updated Joplin to 3.0.13 and installed this plugin (0.15.0), but I have a few of issues and/or don't understand how it works.

Are "plain text" links supposed to get styled automatically? I can Ctrl-click to follow them, but they are not colored or anything.

Using Stylish, horizontal rules that have spaces in between the characters (eg * * *) are rendered strangely. Even with spaces it looks a little strange, with the markdown barely visible and a tiny cursor. I also don't get any side margin like in the screenshot, which causes the header markdown to disappear.

I have enabled the "add extra CSS classes" option.

bild

graphit0 · 2024-07-16T12:48:07.279Z

Before I create the issue, I'd like to ask if this feature is interesting enough to be in scope for this plugin

Clickable URL on image

![ [image label to display](URL) ](/:resourceid)

Example: label underneath the image is supposed to be clickable - opens Youtube page

720×404 48.9 KB

Fig 1. Joplin Tutorial - Joplin Note-Taking App Tutorial - YouTube

Code for the preview block: ![[Joplin Tutorial - Joplin Note-Taking App Tutorial - YouTube](https://www.youtube.com/watch?v=emiwyNQa12Q)](upload://nrUa7d8DKTMlOEkwtnbSLJz8fs6.jpeg)

Use cases

Video/webpage thumbnail preview (can automated with Custom Copy of FoxyTab Firefox Plugin)
app launcher dashboard grid
attachments preview
? potential note preview
webarchive: potential to easily recreate static HTTP elements in note's body

Notes

CM6 renderer supports this feature out of the box but it doesn't work in TinyMC
This feature is more like a markdown hack but surprisingly supported widely enough, although underutilized for some reason

artis · 2024-08-01T06:48:54.980Z

Thank you for your custom checklist setup.
Is there a way to define how it!-inspired checkbox styles are displayed in the viewer or when exported to PDF?
For example, to make that [?], [@], [!] & [~] are also displayed as bullet points or bullet points with specific formatting.

Additionally, is it possible to do the same thing for tags - to have the same highlighting in rendered markdown output?

shikuz · 2024-08-01T09:02:07.311Z

This requires a different kind of plugin (that focuses on the renderer), such as this one (an example for highlighting some tags specifically next to checkboxes). I'm not familiar with a generic renderer customisation plugin for Joplin (where a user might define [x]!it checkboxes in its settings), or one that is dedicated specifically to styling checkboxes.

whitewall · 2024-10-30T18:52:41.192Z

I just upgraded to Joplin 3.1.20 and none of the styling I had for Rich Markdown works. My css file is still there.

Am I the first person to experience this?

ETA: When I switch back to the legacy editor it works again.

my info

Joplin 3.1.20 (prod, win32)

Client ID: 55ce0b2fbc8e4c0c8c573a6923b41b59
Sync Version: 3
Profile Version: 47
Keychain Supported: Yes

Revision: 8199362

Backup: 1.4.2
Better Code Blocks: 1.1.0
CodeMirror Line Numbers: 2.0.0
Ez Table: 1.0.2
Favorites: 1.3.2
Insert Date: 1.0.1
Note list (Preview): 0.0.1
Note list and sidebar toggle buttons: 1.0.3
Note Tabs: 1.4.0
Outline: 1.5.13
Paste Special: 1.1.2
Persistent Editor Layout: 2.2.0
Remove Images: 0.0.2
Reset Checkboxes: 1.0.3
Rich Markdown: 0.15.0
Search & Replace: 2.2.0
Table Formatter Plugin: 1.2.1
Templates: 2.4.0

nokoa77 · 2024-10-31T06:41:54.643Z

Hi, I meet maybe a similar issue, I lost the "yellow highlight" with "double =", I opened an issue here : Issue : "==text==" is not anymore highlighted since Joplin 3.1.20 (Mac OS) · Issue #68 · CalebJohn/joplin-rich-markdown · GitHub

CalebJohn · 2024-11-02T21:20:57.745Z

whitewall:

Am I the first person to experience this?

First but not last!

The == highlighting issue should now be fixed. However, the order of elements has different in the new editor, so some userchrome customizations, will need to be adapted. You can see updated examples in the tips file.

CalebJohn · 2024-11-02T21:26:37.052Z

v0.15.1

Fixed an issue with hover images that caused them to stick around
Updated some internal styling to work with the (now default) new editor.

Unfortunately, the new editor is not one-for-one compatible in terms of styling with the old. So if you are using any custom css in your userchrome file, please review the updated TIPS document. Be aware, that some styles were fully dependent on the old editor, so will no longer be possible (e.g. coloured list tokens).

And finally a big thanks to @personalizedrefriger who did most of the heavy lifting, to get this plugin ready for the new editor!

nokoa77 · 2024-11-07T21:26:12.052Z

Hi, thank you very much for this version and for all your work! V0.15.1 makes ==highlight== working again, but now images doesn't appear anymore when I hover on a image. I notice the same behaviour on Mac and on Windows. Anybody else notices that ?

nonobio · 2024-11-08T07:00:47.958Z

nokoa77:

images doesn't appear anymore when I hover on a image.

Hi, I hardly use this function but I have just done a test with Joplin 3.1.23 and Rich Markdown 0.15.1, and I have the previews of the images which are displayed on mouseover, with CTRL pressed or without, depending on the setting. (edit: I use the new editor, not the legacy)

nokoa77 · 2024-11-08T07:43:28.478Z

thanks, I must have a problem with my config, I will follow on investigation

jb261 · 2024-11-09T15:32:18.004Z

Joplin 3.1.23 (prod, win32)
Rich Markdown: 0.15.1

I updated to latest version of Joplin today along with latest Rich Markdown, and list wrap alignment no longer works. I guess this is expected with the new editor?

If so, I may have to revert to older version of Joplin as the markdown viewer w/o list wrap alignment is very difficult to read if one uses lots of outline formatting.

Edit: I discovered this new version of Joplin has an option to use the legacy md editor, and list wrap alignment works fine with that.