It's true pluging don't work anymore.Missing selections in configurations
3.4.4 has just been released (changelog not published yet) which fixes the plugin issue
v3.4.4
- Improved: Allow editing code blocks from the Rich Text Editor (#12906) (#12841 by @personalizedrefrigerator)
- Improved: Fixed missing filename when a file is shared with the app (#12895) (#12858 by @klaas0)
- Improved: Move several features from Extra Markdown Editor Settings into the main app (#12747 by @personalizedrefrigerator)
- Improved: Rich Text Editor: Improve support for HTML notes (#12912) (#12843 by @personalizedrefrigerator)
- Improved: Updated packages esbuild (v0.25.4), react-native-share (v12.0.11), sharp (v0.34.1)
- Fixed: Ensure merges to revisions during cleaning are synced to the target (#12444) (#12104 by @mrjo118)
- Fixed: Fix error logged when opening the Markdown editor (#12892) (#12891 by @personalizedrefrigerator)
- Fixed: Fix plugin support (#12890) (#12880 by @personalizedrefrigerator)
- Fixed: Fix switching between note and todo on mobile (#12849) (#12822 by @mrjo118)
- Fixed: Rich Text Editor: Make initial search behavior match the Markdown editor (#12878) (#12844 by @personalizedrefrigerator)
1 Like
Sorry about the delay to fix this plugin issue. I actually thought I had released the new version but obviously didn't
1 Like
Joplin Mobile: 3.4.4
Tested without any plugins enabled.
I don't know if this is exclusive to this version. However, I wanted to report it as it came up in everyday usage and I couldn't find a duplicate report here.
In the editor, Markdown links with square bracket sets inside the title are not collapsed by default as expected. They don't collapse when moving the cursor off of them either.
[title [tag]](https://example.com) results in only [tag] and https://example.com being highlighted as link components. The remaining characters incorrectly retain normal text coloration.
I'm not sure that's valid markdown? Probably the square brackets should be escaped
Since Joplin uses CommonMark, the latest CommonMark Spec Links section says the following on brackets inside inline link text:
Brackets are allowed in the link text only if (a) they are backslash-escaped or (b) they appear as a matched pair of brackets, with an open bracket
[, a sequence of zero or more inlines, and a close bracket].
I see Example 512, its explanation prior, its entry into the CommonMark Spec Playground, and the same result in Joplin's reader view as illustrating that brackets inside link text is valid:
The link text may contain balanced brackets, but not unbalanced ones, unless they are escaped:
[link [foo [bar]]](/uri) renders link [foo [bar]].
You're correct that escaped brackets via backslashes or surrounding backticks would also solve the issue. That said, tools like Copy as Markdown use neither (though square brackets in link text is rare to begin with).