[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nano-devel] [PATCH 1/1] bindings: make ^Home and ^End go to top and
Re: [Nano-devel] [PATCH 1/1] bindings: make ^Home and ^End go to top and tail of buffer
Fri, 7 Apr 2017 06:53:47 -0500
On Fri, Apr 7, 2017 at 4:29 AM, Benno Schulenberg
> When using Verbatim Input, those key combos on an Xfce-terminal
> produce the same escape sequences as on xterm.
Good to know; it's covered then.
> But Verbatim Input is not a good way to look at keycodes, because
> normally nano puts ncurses into keycodes mode, but for Verbatim Input
> switches it off for a moment and falls back to escape-sequence mode.
I know. I'm actually trying to make sure that the escape sequences are
covered, because if the user has to use the --rebindkeypad option,
keycodes mode will be switched off and only escape sequences will be
available. The same goes for if the terminfo access is screwed up
somehow; for example, Slackware's rxvt-2.7.10 sets TERM to xterm, but
doesn't generate the same sequences as xterm in many cases, so ncurses
won't return the proper keycodes for it. It's a case of "what should
be" versus "what is", and I certainly wish the two lined up more often.
> The way to look at keycodes is to use --enable-debug and then grep the
> log for "hex codes". On a modern Xfce-terminal, ^Home produces 0x21A
> and ^End 0x215 (but the exact codes are irrelevant, because nano asks
> ncurses for them).
Good to know.