Separate normal modes for browsing / editing

[RobertCraigie]

Currently there is one normal mode which is used both when an editable element is focused and when it is not.

I set it up this way originally as I thought I could "get away with" keeping it simple and just having one normal mode; but I think this simplicity is not really worth it.

With the current setup:

• We have to worry about compatibility with vim motions
• The vim motions will never be full compatible, because of overrides like f
• It's difficult to make it compatible in userspace because its all a single mode

Which are convincing enough arguments for me that we need to change this setup.

Goals:

1. Super easy to configure keymaps in both modes
2. No major breaking changes unless absolutely necessary
3. Mode names are not confusing

So I'm thinking of making this change by

1. Introducing normal-browsing and normal-editing
2. Retaining normal as a glide.keymaps.set() alias for both normal-browsing and normal-editing

Open questions:

1. Are normal-browsing and normal-editing good names?

---

Another option:

• keep normal mode
• add normal-editing
• add n as a keymaps.set() alias for normal and normal-editing

[NonlinearFruit]

I wonder if editing is going to need dedicated modes in general. visual and command modes might have similar issues with browser-specific behavior vs editor-like behavior. Splitting normal mode into two makes sense and normal-browsing and normal-editing are decent names.