Conversation

Roam was the only web outliner which got arrow up/down navigation mostly right, though with some unexpected glitches at EOLs. None of the web outliners support interline selection. OO doesn't either. Bear does great but ofc isn't really structured. And org-mode wins the day.

This sounds so nit-picky and trivial, but I think the difficulty of getting basic editing ops done well in simple outline UX illustrates just how painful it is to make a structured text editor nice enough to live in. There'd be a lot of value in finding a good abstraction here.

Horacio Herrera

@hhg2288

what are "table-stakes editing operations"? after watching the video, I guess is that the selection (caret) bounce too much or in unexpected ways?

7:46 PM · Sep 8, 2021Twitter Web App

Replying to

@hhg2288

Basic navigation and selection should work as well as the text editors which come with your OS. eg when you press the up arrow, the cursor should move up a line, but stay in the same x pos. When line above is short, you should still be able to "round trip" by arrowing down again.

Replying to

and

*This* might be a big part of the challenge — that many people aren’t aware of all these details, and so don’t check for all of them when implementing a custom editor. IMO having a list of all the expected/native behavior would be a valuable first step

Eric Green New Deal Now Gade

@ecgade

Implementing a text editor of any kind on the Web is a shameful nightmare.

Show replies

Replying to

and

I wonder how important that really is once you're either (1) editing text in a block char by char, or (2) editing at the block level instead of at a char level. If I move my cursor outside of the block, maybe I could go into block mode.