Testing - v1.8.1 - Editor Font & Editor Font Settings

[dpoulton]

Pre-release v1.8 is available (Updated 10 May 21)

Quite a big release as I have created any in a while. I think the riskier change is that when installing the new version some settings are going to be moved from the database to a settings.json file. I've tried it my with my own profile and everything seems to work fine but just to be sure you might want to backup your profile folder first. Now that the settings are in this external file it will make it easier to backup and restore a profile. New: Add monospace enforcement for certain eleme…

• Joplin 1.8.1 Portable
• Windows 10 Pro x64 (VM)

Just started doing a little bit of testing on the new pre-release.

Despite the "Appearance" editor font settings stating that leaving the value empty will result in a default monospace font being used, the default is now a proportional font.

The "Appearance" settings has two fields for selecting an editor font:

• Editor Font Family - which works
• Editor Monospace Font Family - which does not work

[dpoulton]

After seeing the settings json file contained the values:

"style.editor.fontFamily": "",
"style.editor.monospaceFontFamily": "",

I realised that having two font selectors was intentional. "Editor font family" appears to refer to the default font for body text and "Editor monospace font family" appears to refer to editor text that has been marked as code. So this field does work but I feel that what they relate to is not exactly clear as it is currently explained on the settings page and only "Editor monospace font family" defaults to monospace.

[tessus]

Yes, it is this item here:

New: Add monospace enforcement for certain elements in Markdown editor (#4689 by @CalebJohn)

The monospace font family is used for:

• Tables
• Checkboxes
• Code (blocks, indented, inline)

[dpoulton]

Thanks. I see it now that I know what these settings fields actually relate to

Basically in my second post I was just suggesting that the text for these settings is amended before the full release so as to inform the user what they actually do. I am quite familiar with Joplin and my initial reaction to seeing the two fields was that there had been a duplication. The descriptive text did not help correct my wrong assumption, in fact the almost identical wording reinforced it!

[CalebJohn]

You're right, the wording can be better. I've created a PR to update the wording, I'd appreciate any comments/suggestions.

[dpoulton]

Suggestion added to the PR.

[mike_2495]

How do I change the font and highlight color of the inline code?

[tessus]

You have to be a bit more specific. Do you mean the rendered one or the one in the editor?

Also, you should have a look at:

Joplin Customization

This page is a collection of CSS tweaks to customize Joplin (e.g. editor, rendering, ...) To discover CSS classes and types refer to this comment Plain editor (no color, no font changes) userchrome.css Joplin version tested on: 1.1.4 div.CodeMirror-lines * { font-size: inherit !important; color: black !important; font-weight: normal !important; text-decoration: none !important; } Example [plain_codemirror] /ref dpoulton comment Dark Theme Mermaid Flowchart (Flowchart only) users…

and

Share your CSS

I would be curious if anyone would care to share their userstyle.css snippets and perhaps a screenshot?

[mike_2495]

The ones in the Rich Text Editor when I'm typing inline codes, which should also give a similar output when I'm exporting the file to PDF.

[tessus]

I don't think the WYSIWYG editor can be tweaked with CSS, but I might be wrong. You probably should open a new topic and not add comments to a topic for a version which is 6 months old.