I really want to say something about this change from a view of a user of Joplin. This is an opinion from a user talking about the change of color style in the recent update. The change to this making the Markdown text more like text instead of code to match its generated HTML views. It is also a g…

Hi @pokemonleo , welcome to the forum! First off, I'd like to say thank you for the detailed post. It can be hard to express frustration and I think you've done an excellent job. I think you've done a great job making your point. For many users, markdown should be treated as code, and for many of t…

[image] CalebJohn: Presently, there are not many consistent contributors to the main Joplin application. I believe one of the reasons for this is that Joplin is a large application, and the barrier to contributing can seem very high. I observed that there have been more people willing to contrib…

[image] CalebJohn: This change was shared and available for 5 days before being accepted. It received no engagement from the broader community. So, I in no way want to criticize anyone, and I know how much work just a few individuals are putting in. I just now followed the link above and tr…

I agree with most of what you say, anything we can clarify beforehand and any way we can get people involved in such decisions is great. In practice we just do what we can though with limited resources. Having the screenshots in the post and the pull request for example would be nice, but it's extra…

[image] laurent: In practice we just do what we can though with limited resources. I totally hear that! And I appreciate what you do. [image] laurent: but it's extra troubles for us to follow conversations on both the PR and forum Very good point. Perhaps a big notice that you should …

[image] CalebJohn: or don't have the time to take an active role in providing feedback. I think many people just don't know how to provide feedback. For sure most people don't know how to provide useful feedback.

I could not agree more with @pokemonleo . Markdown is code. Making markdown look more like a WYSIWYG is antithetical to what markdown is for. For me, this update makes Joplin largely unusable. I am a software developer, and use Joplin because it binds all my notes together in a functional, syncable, …

Did you read the rest of the thread? There's work in progress to improve the styling.

Whilst I'm personally not overly keen on the changes, this really isn't the discussion at this point. What is done is done and we shouldn’t be flip flopping back and forth based on negative feedback after the case. Instead it has highlighted the need for systems both in terms of change communication…

When I made this change, the idea was 1. to make the colour scheme less distracting and 2. to use the same consistent style across the app. For example if a user chooses a black colour for the font, and gray for codeblocks, it's strange that the item lists would look purple and the code block brown. …

Talking about Markdown's CodeMirror theme update

Lounge

Daeraxa 26 January 2022 00:26 20

In case you do want the rest I did have a go at creating the css to restore the rest of the dark theme a while ago - Dark theme syntax highlighting - #4 by Daeraxa

Topic		Replies	Views
Prettier markdown editor? Features	37	5280	13 October 2021
Themes too difficult Support	27	3783	21 November 2021
Markdown editor, style/CSS lost with upgrade Support	8	2144	13 October 2021
Share your CSS Lounge tips-and-tricks	381	78099	29 July 2026
Why is custom CSS an important feature for you? Lounge	22	3319	14 June 2021

Talking about Markdown's CodeMirror theme update

Related topics