Currently I have seen that you can choose the editor type in the settings and the mode (editor or preview) in the notes themselves.
I would like the editor type to be selectable directly in the note, while in the settings I would leave the choiche of default editor.
That way I could keep the editor types and even the preview open in different views so that I could see changes in real time and usually use the WYSIWYG editor and the markdown editor when WYSIWYG is not working as I would like.
Currently the advanced editor is a hybrid of markdown and preview. That’s fine, but I add to the request for a full WYSIWYG editor where you can add formatting effects either with hotkeys or with buttons in a toolbar, as happens in Word. In addition to the pre-existing ones.
Reading the (many) previous comments perhaps this may be an optional plugin, at least in part.
I think it is not a good idea to use an external editor, because Obsidian does not use pure markdown but adds new functions, very useful ones, which I fear would conflict with external editors. And it would mean using an additional program.
Given the structure of Obsidian, when I talk about WYSIWYG I exclude printed page size, since it is possible to export as web, although I would like to be able to specify for a block the alignment or font size.
This would make it easier to insert bulleted lists and links.
I would like for selecting a word to have a command to choose one from existing pages to link to, starting with those that recognize the word as an indirect alias. In this regard, disconnected mentions are activated, and show the number, only after I click on them.
I have encountered an unpleasant problem: If I paste a windows path into a note, the \ are hidden in the display, because they are interpreted as a special character. And even if I write the character manually. A visual editor would paste the text preserving all the characters. By storing them with the corresponding escape sequences.
I would also like there to be the possibility of storing a block of text as-is, similar to the PRE of HTML.
Even here, as I write this post, I had to enter the character twice. I find it “strange” in a semi-visual editor to write the source.
In fact, I expect escape characters surrounded by spaces to be identified as characters and not escapes. And that common objects, such as paths, should also be identified as such.