[Looks like the mail server is having some indigestion and delays. Hopefully it will sort itself out.]
On Sat, Feb 25, 2017 at 08:22:44PM +0100, Guyzmo wrote: > That being said, if we were to make it possible to change the "abort" > key, we should make it possible to change to any key, not just ESC or > <C-g>. > > So maybe adding a command to define and validate what key is > bound to the abort feature and have mutt_getch() check against that key > string? Maybe having several keys mapped to abort could be an idea? > > Then making sure that no binding has that key, and prevent the binding > command to bind something to that key would make sense, to avoid any > surprise. Most of the questions I have seen in the past have only been about "how to get out of the compose menu". I wonder if it wouldn't be a better compromise to just add an <abort> function for the compose menu. Leave ctrl-g as the "universal" abort deep inside mutt_getch(), but let the user add an additional binding for line input. The changes required for going deeper, which you have nicely enumerated, make me worry it's too intrusive and too much effort for a minor additional configurability. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
