How to set the default markup language to HTML (instead of markdown) for new notes?

Support
21

Not the same request but essentially the same problem in https://github.com/laurent22/joplin/issues/6815 about Markdown destroying copy & pasted tables just yesterday.

22

I've actually updated it if you are still interested. It now has a new command newNoteHtml which will create a new, blank HTML type note and focus the title.

1 Like
23

Thanks a lot for the plugin! I've been testing it for a few days now, and everything seems to work as expected. What's interesting is that when the note is set to HTML, then the RichText editor formats everything as such too, adding all the HTML tags and such instead of Markdown. Because of this, the note looks different visually as well. It would probably be needed to have some custom CSS to make it more consistent with how Markdown is displayed in it.

24

So I did notice this before, if you actually swap notes without changing editor you will find that the default style applies again. Happens on both editors.

I know that it isn't an issue with the import and webclipper html because it creates the styles in the html directly rather than relying on the CSS.

25

Hmm, so the problem seems to happen when you switch from RichText to Markdown and then back to RichText. If you switch to a different note, and then to the original one, then the styling is correct again.

I've checked with DevTools and it appears that Joplin styles are simply not applied at all, so the note is displayed using the default TinyMCE styling.

26

Yeah, exactly what I saw, not really sure what the correct solution would be here, its interesting that Joplin only applies the default styling on note change and not when first selected - possibly a bug that is just never been seen (and isn't even an issue in normal use)?

If you use dark theme it is more obvious and you can see it also happens in the md editor on the viewer.

27

This is a fascinating read. I had no idea that a note could be labeled as such and treated differently.

The Rich Text Editor: even editing markdown is problematic with the rich text editor, so I never use it. In fact, I removed the toggle button for it from the UI. I mean, I once had this document with copious notes in HTML comments and... I made a few edits one day in the rich text editor and POOF all my notes were gone. And it does other unpleasant things.

Anyway. If sticking to the normal text editor is something desired by folks here, Just add this to your userchrome.css configuration file (Options > Appearance > Custom stylesheet for Joplin-wide app styles):

/* removes the WYSIWYG button */
div.editor-toolbar div button {
	 display: none !important;
}

An aside: I do quite a bit of advanced things with CSS and Joplin and markdown. Tables though ... notoriously challenging with markdown (and HTML for that matter).

28

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.