Plugin: Rich Markdown

Plugins
262

I would be too, it's an annoying situation. You could probably try disabling this plugin for a few days to see if the crashes go away. As you mentioned, there isn't much useful information yet, so this might be a bit of a waiting game.

I think if I understand you correctly, the trouble you're facing is that you're losing footnote highlighting/formatting when switching to the rich text editor? If thats right, then there isn't much I can do to help you here. The purpose of this plugin is to extend the functionality of the Markdown/plain text editor, it doesn't touch the rich text editor at all.
You could perhaps suggest a plugin.

There is a document about the limitations of the rich text editor that you might find useful.

1 Like
263

Is there a way to make bullet points made with dashes ("-") render as dots?

I'm only able to find solutions for bullet points made with asterisks ("*") like this one.

264

You can copy the one that you linked, but change the last block of text to this


.cm-variable-2.cm-overlay.cm-rm-list-token {
    /*make markdown tokens for list into dots*/
    color: transparent !important;
    background-color: var(--g-unemphasizedSelectedTextBackgroundColor) !important;
    height: 6px;
    width: 6px;
    border-radius: 50%;
    display: inline-block;
    vertical-align: bottom;
    margin: 0 8px 8px 0;
}
265

Thanks. I've actually tried that already but it breaks rendering for numbered lists as they are also shown as dots. Also when using asterisks for bullets now two dots are shown.

266

In that case there likely isn't a way to achieve what you want using CSS only.

267

I have a long note (~2000 lines) where the rich markdown plugin leads to lagging. I can finish typing a full sentence before the letters appear. If I deactivate the plugin, editing works flawlessly.

Windows 10, Joplin 2.5.10, Rich Markdown Plugin 0.7.3, but the problem started to occur months ago.

268

Is that a note you can share?

269

Can't share this particular note, but it happens for this Lorem Ipsum note with 2800 lines too. With the Rich Markdown Plugin activated, typed letters and sentences appear with a delay of around a minute. With the plugin deactivated: No problems.

2 Likes
270

Thanks for sharing this @Prinplup, it was super easy to reproduce using it (although luckily changes appear after about 5 seconds for me, not 1 minute). This will be fixed in the next version.

The performance issue was due to some code for highlighting code block backgrounds. While this was added to the main app in v2.3.4, this plugin supports v1.8.0 and up. Due to some other changes, I was planning on bumping up the minimum version to v2.4.0 anyway, so I'll go ahead and remove that functionality at the same time.

5 Likes
271

Is there a way to make a box of content with expand/colapse? (Such as a 'read more').

1 Like
272

With the spoiler plugin :thinking:

2 Likes
273

Or the Folding in Code Mirror Editor plugin if you want something that works in the markdown editor. You can do a forum search for more info. But this thread isn't really the best place to ask.

@CalebJohn I'm noticing that if I delete the text that inserts an image (usually created using the web clipper) the image seems to freeze in the editor, no matter what note I go to. I'm guessing this is because of the "Enable image popup even when Ctrl (or Opt) is not pressed" option I have selected, but obviously it shouldn't stay popped up after it's markdown source is deleted.

274

Or use the details tag like below. I came across this on some other post on the forum a long time back. I find it particularly good with PDFs, to hide them until the heading is expanded.

<details>
<summary><b>Read more</b></summary>

Leave a blank line before the content that's to appear

Markdown **works** fine between *these tags*
</details>
Read more

Leave a blank line before the content that's to appear

Markdown works fine between these tags

275

v0.8.1

  • Breaking!! Bump min Joplin version to 2.4.0
    • This update uses some newish features of Joplin and as such requires
      all users to have Joplin 2.4.0 and above
  • fix: Remove Code block background highlighting
  • feat: Add line highlighting for blockquotes
    • This makes it possible to have blockquotes with a vertical bar
  • chore: remove usage of cm-search-marker in favour of cm-rm-highlight
    • Most users won't notice a difference, but those that customized the
      colour might
  • fix: Editor was jumping around when images were enabled and present in a note

The new version should be available for download shortly!

5 Likes
276

@CalebJohn The editor is still jumping around for me when I have "Render images below their markdown source" enabled. Whenever I scroll to a location, a second or so later the location will jump a bit which is pretty disruptive.

277

Can you double check that you have v0.8.1 installed and have restarted the editor since? If that checks out, can you maybe send a video?

v0.8.1 removed the plugins ability to do any scrolling, so if you're still experiencing this then it's likely a bug that will need to be fixed in the core app.

278

I've confirmed that I have v0.8.1 installed and have restarted the editor. I've tried this on both Linux and Windows and whenever that option is enabled, I see it happening:
inline_image_jump

279

Thanks for sharing the video, that's definitely annoying. This is different from the bug caused by this plugin, it only happened when the editor was open alone (no viewer).

My first thought would be that maybe this is caused by the "Better Markdown Viewer" plugin because it has some ability to scroll. But I can't duplicate your issue even with it installed.

Could you try disabling all plugins except for Rich markdown? I'm wondering if it's possible that this is a bad interaction between multiple plugins.

1 Like
280

The problem still persists after disabling all plugins except for rich markdown. It happens both on split view and editor view. Have you tried it on a very long document with a bunch of pictures?

1 Like
281

I've been using a clipping of this page.

long.jex (1.7 MB)

Can you share an example note that consistently doesn't work for you? That is if the attached note doesn't demonstrate this issue for you.