still very dangerous one-key shortcuts # and x

[rubo77]

I think the main purpose of this add on is to unset the dangerous keys, that cause havoc if you type them uncontrolled because you happen to have the focus on the wrong window, so those new shortcuts should not be in the defaults and only be optional for users that are not afraid of those single-key-shortcuts:

• "#": "cmd:cmd_delete",
• "x": "cmd:cmd_archive",

the others are harmless and just open some windows ;)

so better set those as default to

• "#": "unset",
• "x": "unset",

[wshanks]

Unsetting dangerous keys was not a use case I had in mind when I created tbkeys, but it appears to be a popular one and I am happy to support it. I think really between this issue and #41 you are making a case that the default install should set no key bindings.

The current default bindings are the ones I use, and I thought including them would be a nice example for other users to start from rather than a blank page. However, the text could be moved to the README for copying and pasting into the preferences.

[tvercaut]

Adding an FAQ including typical configs would be great for newcomers. I was looking for a means of replaing the "a" shortcut for something less error prone (following the loss of several previous add-ons after being upgraded to TB78) and am glad I found tbkeys-lite!

For now, this is what I used to match the archive shortcut from outlook on Mac OS (which I also have to use from time to time):

{
    "a": "unset",
    "ctrl+e": "cmd:cmd_archive"
}

I guess I will now also start unsetting other one-key shortcuts which have been bothering me since keyconfig stopped being supported.

[rubo77]

... that the default install should set no key bindings.

yes, but not just set no config, better set each config for the keys, that they were without this plugin, for example set expliciltey "a" to "cmd:cmd_archive", so you see intuitively, what you need if you want to move all one-key-shortcuts to something else.

[wshanks]

Hmm, maybe those could be optionally populated by a button or at least documented on the wiki. My concern with populating them by default is that the way the "unset singles" button works now is that it only unsets the keys that do not currently have a shortcut set. I like it working this way to avoid someone accidentally overwriting their settings.