So, other than the accessability, is there any reason for a non-mobile user (or non-mobile plugin users) to switch. I ask because switching to the beta loses all of my custom css (which I understand was never guaranteed to last).

Here's a non-exhaustive list of changes:

Keyboard shortcuts

  • Bold/italicize/code shortcuts act more like they do in a WYSIWYG editor. For example, if | denotes the cursor:
    • Pressing ctrl-b: **bold|** -> **bold**|
    • Pressing ctrl-`: `co|de` -> code| (all selected).
  • Pressing ctrl-` twice creates a code block (rather than toggling inline code twice)
  • The Vim keyboard mode supports copy/paste through the "+ register

Autocomplete

  • Ordered lists auto-renumber in some circumstances.
  • HTML tags autocomplete: typing <p>| autocompletes to <p>|</p> (where | is the cursor).

Find

  • The find/replace dialog has replace.
  • It's style is still the CodeMirror 6 default --- changing the style of the dialog is planned.

Syntax highlighting

In CodeMirror 5, it was necessary to add markdown="1" to HTML elements to get markdown syntax highlighting inside of them. For example,

<div>

In CM5, `markdown` here is **not** highlighted. However, it is in CodeMirror 6.

</div>

This matches Joplin's rendering in the viewer.

2 Likes