Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

implement motion keys to match application? #270

Open
fncll opened this Issue Nov 24, 2011 · 6 comments

Comments

Projects
None yet
4 participants

fncll commented Nov 24, 2011

Idea: implement motion keys for navigating through peepopen dialogue that can match the application (vim, emacs, etc)

Owner

topfunky commented Nov 30, 2011

Are there specific ones you're missing?

For Emacs, Ctrl-n (next), Ctrl-p (previous), and Ctrl-m (enter) work already.

fncll commented Nov 30, 2011

I was thinking j,k, ENTER while navigating the list (aka vi/vim)

Owner

topfunky commented Nov 30, 2011

How do you imagine that working? I haven't been able to figure out how one would navigate Vim style in PeepOpen.

Right now if I type "j" or "k", it searches for those letters.

Hitting ESC hides the PeepOpen window, so it would be hard to go into command mode as you can in Vim.

Hitting ENTER choose an item already.

Ctrl-j and Ctrl-k would be an option, except that Ctrl-k is already used by the operating system for "kill line" (from Emacs).

fncll commented Nov 30, 2011

I'm not in front of a machine with PeepOpen at the moment, but I was imagining that if one hits tab to bring the list to focus, then j/k would move down/up ... tab again would bring focus back to the search/text/whateveryoucallit area.

tgray commented Dec 12, 2011

It'd be nice if you could at least toggle on the Ctrl-j and Ctrl-k bindings for down and up. That is, if you can override Ctrl-k for 'kill line'. I know not everyone would be happy with that, so it'd be nice if it was an option.

hk0i commented May 18, 2012

I was about to put in a similar request, and I agree with tgray completely. This is how the vim command-t plugin works, I assume I'm not the only one making the switch from command-t in vim to this.

The Command-T plugin also allows you to bind other keys to open files in split or vsplit mode. I'll go see if I can find a more relevant place to post more about that, specifically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment