Keyboard shortcuts

[andrei-a-papou]

Feature Request

1. More keyboard shortcuts
2. Configurable keyboard shortcuts

What problem does it solve?

1. It would be the next step towards a more complete keyboard-driven workflow made possible with sleek. When properly implemented, keyboard-based workflow is very efficient and fast, which allows for an even better user experience.
2. Because it's hard to design keyboard shortcuts in a way that all (or even most) users find helpful, a better approach could be to expose sleek's actions and allow users to configure keyboard shortcuts for them via e.g. a JSON configuration file.

Proposed keyboard shortcuts

1. Ctrl+PageUp and Ctrl+PageDown to cycle through open todo.txt files -- many apps do this, e.g. browsers
2. Ctrl+Shift+PageUp and Ctrl+Shift+PageDown to re-order open todo.txt files (currently there seems to be no way to change the order)
3. a shortcut to focus the main pain with todo rows (perhaps the first item or due date button) -- this one I personally miss badly
4. using the Menu key to pop up the context menu on a todo (right now this is only possible with a mouse)
5. TBD

[amariusz]

• Ctrl+PageUp and Ctrl+PageDown to cycle through open todo.txt files -- many apps do this, e.g. browsers
• Ctrl+Shift+PageUp and Ctrl+Shift+PageDown to re-order open todo.txt files (currently there seems to be no way to change the order)

I second that. Those are also the main shortcuts I miss. They don't necessarily need to be configurable as many apps use them (like Chrome).

Ctrl+W currently closes Sleek window. I'd prefer it to close current tab. Ctrl+q or Ctrl+shift+w are common for closing the main app.

[c33s]

please allow us to customize the shortcuts like in doublecommander

[andrei-a-papou]

please allow us to customize the shortcuts like in doublecommander

To me, a UI like in the picture above is a vast overkill :) Just a documented JSON/YAML config file would be fine, IMHO.

[dnngll]

2. Configurable keyboard shortcuts

+1. A very important feature imho.

A simple config-file would be perfect. Certainly no need for something like #645 (comment)