[Top][All Lists]

[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

From: Benno Schulenberg
Subject: Re: [Nano-devel] [PATCH 1/1] bindings: make ^Home and ^End go to top and tail of buffer
Date: Fri, 07 Apr 2017 11:29:39 +0200

On Thu, Apr 6, 2017, at 21:43, David Ramsey wrote:
> On Thu, Apr 6, 2017 at 2:04 PM, Benno Schulenberg
> <address@hidden> wrote:
> > This is true for version 0.6.3 (on my Xubuntu system), but on version
> > 0.8.4 (on a Manjaro install) those four Control combinations produce
> > distinct codes (not escape sequences) and work beautifully.
> My Slackware system is still using 0.6.3 as well.  I make it a point of
> covering the escape sequences just in case, and it may be that newer
> xfce terminals generate different sequences that nano already covers.
> I'll check that when I can update.
> Or would you be willing to find out what escape sequences it generates
> on your Manjaro system, so I can check sooner?  (As in, if you go into
> verbatim input mode and press Ctrl-Home, Ctrl-End, Shift-Ctrl-Home, or
> Shift-Ctrl-End, what does nano spit out for them?)

When using Verbatim Input, those key combos on an Xfce-terminal
produce the same escape sequences as on xterm.  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.  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).


-- - The professional email service

reply via email to

[Prev in Thread] Current Thread [Next in Thread]