I'd like to see this.

Yep, definitely this functionality. Checkvist seems to be mostly focused on using commands that are best suited to people who rest their hands in the home row / touch type, so having to use arrows makes no sense  — it is less ergonomic, slower and more imprecise than the alternatives near the home row, so big +1 to this.

The ability to have what https://github.com/nicosantangelo/checkvist-extended-commands offers plus additional vim-style bindings for other commands / keybind configuration would be HUGELY beneficial.

Thank you so much for the link to the chrome extension! It responds a tad slower than using the arrow keys, so I still vote for this (h/l fold/unfold) to be a feature. Also I really want to be able to fold the parent node from a child node. This is possible pressing the left arrow two times, but pressing h two times throws me back to the list overview.

A third-party Chrome extension which allows to set some custom key bindings: https://github.com/nicosantangelo/checkvist-extended-commands.

This allows for very easy browsing of the outline. No moving the arm to the arrow keys.

I've created an extension to get some of this features https://chrome.google.com/webstore/detail/fofahggocngkjhdjmpplnaebognbkfmo

It's implemented on top of the existing Checkvist shortcuts so it has some caveats but it mostly works. Right now, it adds:

l - Expand node (same as `→`)
L - Focus the list item (same as `Shift →`)
h - Collapse node (same as `←`)
H - Un-focus the list item (same as `Shift ←`)
o - Add below (same as `enter`)
O - Add above (same as `alt+enter`)
G - Go to the last item in the tree (same as `End` or `Fn+Down`)
alt+g alt+g - Go to the first item in the tree (same as `Home` or `Fn+Up`)

For more info you can check https://github.com/NicoSantangelo/checkvist-extended-commands

Another case for vim-style expand/collapse: https://checkvist.uservoice.com/admin/forums/2121-general/suggestions/17589709-add-new-collapse-expand-short-cut-like-in-vim

Would like to be able to select the last level with a quick keystroke combination - I often want to collapse an outline to the second level, which currently takes several taps and tabbing.

I would love to be able to remap the current keyboard shortcuts. I have been using vi shortcuts for many many years and the current Checkvist keyboard shortcuts drive me crazy.

Let's just start with the font colours on buttons 1-6, make editable ones for 8-9 !

Yes! I'm all for the ability to customize keyboard shortcuts. For example, I'd rather have something other than Space to indicate a completed task. It's just too easy (for me) to fat-finger the Spacebar.....

I can imagine named keyboard layouts that could be like themes or profiles. As part of a user's setup preferences. You might allow two keyboard for the free and ten for the Pro account.

I've used GMail's and Chrome's shortcut keys layouts. I would find the transition to Checkvist easier with a similar keyboard layout.

The ability to modify shortcut keys would be handy. For example, on my macbook the ctrl - right and left arrows are used to move from one desktop to another.

That last comment was from me, not Anonymous.

I'm keen for using the alt key instead of the control key to modify the arrow keys. And please stop popping up each line's detail each time the modifier key is pressed. Thank you.

Hello Joseph,

Could you clarify what you propose shortcuts 'u' and 'i' shortcuts for?

Thanks,

for now you should bind left and right and right to letters on the keyboard like you do for j,k--up,down. It would make checkvist even more faster.

may i suggest "u" and "I" as it is right above j and k

I've decided re-formulate the issue - to support shortcuts configuration. Not very easy, but possible.

If you exposed the bindings interface, I'd be happy to create a set of vim bindings (or at least a subset that doesn't conflict with current settings).

I'm afraid there may be conflicts with existing current shortcuts.
For instance 'hc' shortcut is used already, so we cannot use 'h', 'as' shortcut is also used for "asap" tasks, and it prevents us from using 'a'.
'oo' shortcut is used for checklist options popup also.

So, to implement this, we have to provide totally different shortcut map (or allow user to customize tons of shortcuts).