I want to create a WYSIWYG editor for markdown, and I want it to be keyboard-driven with vim editing philosophy.

I want the editor to have rich formatting, rather than the equally spaced cells of characters in the terminal. This would enable rows having different text sizes, usage of non-monospaced fonts, editing RTL languages such as arabic or hebrew, and bypass other terminal limitations.

Embedding neovim would be nice in theory, enabling all compatible vim features. But it seems to come with great difficulties, since I am forgoing the entire rendering philosophy that neovim depends on (equally spaced cells of the terminal).

SO I am thinking it would be better to emulate the vim features I want, starting with basic keybindings and motions, and go from there. But I am worried that I might end up regret this choice? It seems that embedding neovim is too monumental of a task for what I want to do. Am I mistaken?

  • matcha_addict@lemy.lolOPEnglish
    1·
    6 months ago

    Thanks for the pointers!

    You might hit some challenges like how to handle style elements. For example:

    <cursor>*bold*

    Moving the cursor to the right of the b will take two key presses in nvim but would typically be one key press in a WYSIWYG editor.

    I’ve thought about this actually, and Youre right it will require some handling. In the first version of the editor, I will still include the special characters, such as the * for bolding. But I will also style it and what’s after as bold.

    I really like the render-markdown plugin, but my deal breaker was RTL language, since Arabic is a native language to me that I wish to write in vim.