Re: Key binding problem

2022-11-06 Thread Kevin J. McCarthy
On Mon, Nov 07, 2022 at 01:03:31AM -, Jeffery Small wrote: One thing to note is that on the help page, these assignments are being displayed as the characters A, C, D and ? which could generate confusion since these are not the actual characters which also show up and are bound to other act

Re: Key binding problem

2022-11-06 Thread Jeffery Small
"Kevin J. McCarthy" writes: >On Sun, Nov 06, 2022 at 07:31:44PM -, Jeffery Small wrote: >>I just tried that, but the debug file reports the same thing shown on the >>command line when the key is pressed. Here are the results: >> >>Keypad / key: Oo: Char = A, Octal = 1101, Decimal = 577 >>

Re: Key binding problem

2022-11-06 Thread Kevin J. McCarthy
On Sun, Nov 06, 2022 at 07:31:44PM -, Jeffery Small wrote: I just tried that, but the debug file reports the same thing shown on the command line when the key is pressed. Here are the results: Keypad / key: Oo: Char = A, Octal = 1101, Decimal = 577 Keypad * key: Oj: Char = C, Octal =

Re: Key binding problem

2022-11-06 Thread Jeffery Small
"Kevin J. McCarthy" writes: >Have you tried running mutt with '-d 1', running , and looking >at ~/.muttdebug0 as you press those keys? That might list the full >sequence of keys mutt is seeing when you press the non-working keys and >give a clue. I just tried that, but the debug file reports th

Re: Key binding problem

2022-11-06 Thread Kevin J. McCarthy
On Sat, Nov 05, 2022 at 07:25:46PM -0700, Jeffery Small wrote: I tried using the what_key function, but it's of little use as it only reports the last character of the escape sequences. Have you tried running mutt with '-d 1', running , and looking at ~/.muttdebug0 as you press those keys? Th