I curse myself for falling for it again, navigate to the previous line and hyperextend my pinky uncomfortably to select the completion item I want using the arrow down key
I really hope this can be fixed, but at the same I feel like there must be some kind of technical reason behind it not being already implemented – it just feels too obvious, pretty much every other tool works like this: macOS menu bar item search, xCode completion, etc etc
Extra note: I actually really like using Ctrl-n/p/f/b for navigation normally and wouldn’t want to disable these shortcuts.
Actually these hotkeys are used in many editors to move the cursor down to the next line. Why should bear change that standard behaviour, especially since you can use the standard up and down arrow keys?
In general in most conforming apps Ctrl-n/p and down/up-arrow actions are synced. This is plain common sense and is true even for Apple’s own apps – see xCode for example. So Bear’s behavior is definitely not standard, this is a bug.
Note that I’m not asking to change the normal behavior of Ctrl-n/p keybindings, they should still move the cursor up and down, but not when there’s a completion popup open!
