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.
2 Likes
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!
9 Likes
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 ?
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)
1 Like
thanks, I must have a problem with my config, I will follow on investigation
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.
1 Like
Joplin 3.3.13 (prod, linux)
Rich Markdown: 0.16.2
Ctrl+Click no longer opens links despite having Follow note links with Ctrl (or Cmd+Click) and Require Ctrl (or Cmd) when clicking on elements (links and checkboxes) enabled. Subsequent clicks on the same link only create multiple cursors.
It's still working for me with the 0.16.2 version,
try disabling the rich markdown plugin plugin | restart joplin | re-enable the plugin | restart joplin
or if that doesn't help, try uninstalling/re-installing the plugin
I noticed when I was working on my own plugin that plugin keyboard shortcuts sometimes stop working after a plugin is updated to a new version, until you either disable/re-enable the plugin or uninstall/re-install the plugin (plugin api bug?)
Still facing the same issue not only after re-enabling and reinstalling Rich Markdown with application restarts in between, but also after disabling all other plugins.
ah, I think the reason it's working for me is because I'm running 3.4.x, which now includes the ctrl + click feature out of the box:
- Allows following Markdown links with ctrl-click from the Markdown editor (similar to functionality from @CalebJohn's Rich Markdown plugin).
I tested disabling rich markdown's follow link setting and ctrl + clicking links in the md editor still works for me, so I'm guessing that's why
I found the actual issue: following links with Ctrl+Click using the latest Rich Markdown version only works with the Use the legacy Markdown editor option disabled.
1 Like
Hello, I just updated to v3.4.6 today (from 3.3.13) and wrapped list alignment is no longer working for me. I am using v0.16.2 of Rich Markdown, and I have the Align wrapped list items to the indent level box checked in the plugin settings. This is with Use the legacy Markdown editor unchecked in the General Joplin settings (with that box checked, the plugin does not work at all, which I gather is a known issue). I have tried disabling/restarting/uninstalling. Thanks in advance!
1 Like
This is also a known issue indent wrapping only worked in the legacy editor, which is broken from 3.4 onwards. I have created a fix and am currently testing it now.
The Joplin team will also likely implement the same feature in the core app, Add support for line-wrap indent aligning ¡ Issue #12996 ¡ laurent22/joplin ¡ GitHub
4 Likes
great, thanks very much for the quick reply!
feature request: allow âenterâ, to create a single line space, rather than having to use âshift/enterâ. iow, have âenterâ work the same as in markdown.
I updated Joplin to 3.4.10 and it freaked out and I had to go into Safe Mode (I know I should have copied the bug report, but didnât), so rolled back to 3.4.7. Both with 3.4.10 and now with 3.4.7 I am not able to do Ctrl-Click to mark a checkbox as complete.
Is this an issue for anyone else?
I am on Rich Markdown 0.16.2
ctrl + clicking checkboxes was added as native functionality in 3.4.x, so it's working for me even if I disable rich markdown: Desktop,Mobile: Markdown editor: Toggle checkboxes on ctrl-click by personalizedrefrigerator ¡ Pull Request #12927 ¡ laurent22/joplin ¡ GitHub
rich markdown is working for me in 3.4.10 (I mainly use it for the feature to render html img embeds and that's working)
If you use the legacy editor, then this could be because of a bug in v0.16.2, which is now fixed in v0.16.3.
Otherwise you should check your settings. Joplin 3.4.10 introduced a change that disables the ctrl-click setting in the rich-markdown plugin. Thereâs a good chance that itâs simply not enabled in the rich-markdown settings. Although as bwat47 noted, that feature is now built-in to Joplin, so I canât say for sure why it isnât working.
Thanks for the replies. I updated to v.0.16.3 plus also back to Joplin 3.4.10 and all seems well again. It was likely another plugin and Iâll follow up with that separately.
Iâll add here that:
- Installing Joplin 3.4.10 hadnât disabled the ctrl-click setting in Rich Markdown for me either time - regardless I had toggled this a few times to see if it did anything
- I donât seem to get the ctrl-click experience in built-in Joplin, even with Rich Markdown disabled
Sounds like youâre still using the legacy editor. You can check under Settings > General > Advanced, and see if this option is ticked.
The new functionality (and now many plugins) rely on using the new editor. Some plugins (like rich-markdown) are still in the transition phase where there is only partial support. I believe the legacy editor option will be removed at some point in the future, so if youâre still using legacy, you might want to give Joplin a try without it.