Why did editor pane change after update?

[mdalypgh]

Operating system

Windows

Joplin version

3.4.6

Desktop version info

Joplin 3.4.6 (prod, win32)

Device: win32, AMD Ryzen 7 5800H with Radeon Graphics
Client ID: b4223f63eed946bcb2bd594f6c77c80b
Sync Version: 3
Profile Version: 48
Keychain Supported: Yes
Alternative instance ID: -

Revision: 4128061

AlertsPerfect: 1.0.1
Backup: 1.4.3
Cursor Sync: 2.1.0
Embed Search: 2.0.0
Extra Markdown editor settings: 1.11.0
Freehand Drawing: 3.1.0
Hotstrings & Hotkeys: 1.0.0
Inline tags: 1.3.0
Markdown table calculations: 1.0.5
Markdown Table: Colorize: 1.2.0
Markdown Table: Sortable: 1.3.0
Math Mode: 0.8.2
Note Variables: 2.0.0
Pseudocode Support: 0.1.0
Quick Links: 1.3.2
Recipe Scaler: 0.9.2
Search & Replace: 2.2.0
Templates: 2.4.0
Text Colorize: 1.2.5

Sync target

OneDrive

Editor

Markdown Editor

What issue do you have?

After updating to the latest release, the menu automatically toggled off but the real issue is that the editor pane changed so I only see the heading codes (#, ##, ###, -, etc), etc when my cursor is on that line. Once the cursor leaves that line it goes back to looking like the preview pane. I want to see those controls all the time, but I cannot find where that setting is.

First, is this an intended change?

Second, how can I change this back? Where is the setting?

The editor pane should not be exactly like the preview pane. That seems to defeat the purpose of the two pane system.

[tomasz86]

Please see Desktop, Mobile: Move several features from Extra Markdown Editor Settings into the main app by personalizedrefrigerator · Pull Request #12747 · laurent22/joplin · GitHub. You can go to Options → Note and disable the newly added features there.

[mdalypgh]

Thanks. That did it.

[bwat47]

You make a good point about the split view

Personally I like the new markup rendering feature a lot, but I only use the editor view (no split view, hardly ever use the preview)

I think for the split view, it would make sense if it ignored the render markup setting and always rendered the markup in the editor (given that there's a separate preview always being displayed in that mode)

[brenda]

The main reason I like markdown is that it is NOT WYSIWYG.If that sounds weird, please google “Kernighan’s Rebuttal”. Specifically, a text editor running on text+markup is a much more powerful tool than any visual editing system will ever be. It takes more practice, but I edit text for a living.

So, I absolutely understand the point of your visual editor and of making it the default. But please keep plain text editing an option for us keyboard monkeys.

(Edit: Apparently “Kernighan’s Rebuttal” has disappeared off the face of Google… The piece revolved around the observation that visual systems struggle with structural information. Simple example: in a word processor, it takes effort to see whether that 16pt bold text is a header or just manually formatted that way. In systems like Markdown, HTML, or LaTeX, it is obvious.)