The post below was supposed to go to the mutt-dev list but accidentally got posted to mutt-users. (Don't ask!)
Anyway, for those following along, with the help of Vincent Lefevre and Ian Collier, the answer turned out to be that the troublesome keys were actually defined in the xterm terminfo definition as function keys. Once the escape sequences in the .muttrc file were replaced with <f21> through <f25>, the keys were then recognized within mutt. So the problem has been solved. Thanks to everyone who responded. All the ideas were helpful in getting me to a solution. Regards, -- Jeff Jeffery Small <j...@cjsa.com> writes: >Vincent Lefevre <vinc...@vinc17.org> writes: >>> I wrote: >>> However, none of the bindings or macros that have a ";" in them are working >>> when mutt runs. >>I have no such problem. For instance, I have: >>bind index,pager "\e[1;3A" previous-unread >>so that I can type Meta-Up to trigger this function. >>> Outside of mutt, on the command line I can type ^V and the key and see that >>> it is definitely issuing the proper string. >>No, this does not guarantee to give the same string because Mutt >>runs in app mode, and escape sequences can be different in this mode. >>You can check with "tack". In "tack", type n f n then try your keys. >>For instance, on the commande line (or in cooked mode), the left arrow >>yields ^[[D, but in app mode (e.g. in tack), it yields ^[OD. >I installed tack(1). When pressing the keypad keys I get (for example): > ^[[20;2~ (kf21) > ^[[1;5P (kf25) >as well as the expected result for all other keys. All of these keys with >';' in them work without problem in every other program I use, such as >vim(1) and my nn(1) news reader. >>> All key assignments without a ';' in them work fine and all that >>> include a ';' fail. >>You can try to type the individual keys like Esc [ 2 0 ; 2 ~ to >>see if these key assignments actually work. If they work, then this >>is because the special key does not give the sequence you expect. >I tried this for quite some time with different key combinations. It >almost always fails with mutt reporting: "Key is not bound. Press '?' for >help." >However, every once in a while, these manually entered sequences DO work! >They might work two or three times in a row and then stop working again. I >have tested over and over and I cannot find any sequence of actions that >will reproduce the condition where they start or stop working. I have >never yet seen a case where the actual keypad key worked. >Remember that mutt is reporting that these sequences are properly defined >in its internal tables. >Does any of this shed additional light on what might be wrong. I'm >perplexed by the fact that the manual entry very occasionally works. This >seems very odd. >>-- >>Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> >>100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> >>Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
