Hmm, the jump mode issue is strange; can you please file an issue as a starting point?
As for the error message, it didn't wipe out your file; it opened a new buffer with the error message. You can switch between buffers using Tab. There's a full keymap listing available through a command called "application::display_default_keymap" that you can invoke by hitting 0 in normal mode and searching for it.
I’m on my phone so I haven’t checked. But my biggest grip with vim/emacs is discovery of new commands (for noobs or experts).
What are you doing to solve that?
Sublime Text fixes this by allowing you to do fuzzy search to access all the commands (command-P). Once you find your command it also displays the keyboard shortcut next to it so that next time you can use it instead.
You can fuzzy search Amp's commands, or display a buffer with a complete listing of all of them[0]. You can also view the default keymap[1] right in the editor.
As you note in there, it isn’t really made for discovery. It’d be great if you could see the key binding next to the name of a command when you press ‘0’.
Other feedback: fuzzy search doesn’t work well for me. For exemple if I don’t write the folder name I can’t see the file. If I press backspace it deeted the entire search.
It’s be great to have “press ?” Or something like that when you open the editor. Like that you know directy how to see the key bindings.
You can press "?" when you open the editor to read quick start guide. :)
As for the fuzzy search, it's working as intended. Have a look at the docs[0] for an explanation of the matching algorithm, UX, and the reasoning behind it; it's intentional, I promise.
Love the idea of displaying the key binding next to the command!
So I tried a new file and then the error message wiped out my sample text.
Also, I don't see how to switch between buffers?