From: foser <foser@foser.dyn.warande.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Strange keymappings in nano
Date: 20 May 2003 19:53:48 +0200 [thread overview]
Message-ID: <1053453228.8442.1.camel@rivendell> (raw)
In-Reply-To: <200305201630.13549.aoyu93@dsl.pipex.com>
On Tue, 2003-05-20 at 17:30, Peter Ruskin wrote:
> On Tuesday 20 May 2003 16:24, Peter Ruskin wrote:
> > If I'm editing a file that has long lines, using `nano -w`, the Home
> > and End keys don't work as expected.
> >
> > ^a and ^e work OK as Home and End respectively, but:
> > End inserts "F" at the line start and Home inserts "H" at the line
> > start.
> >
> Forgot to mention, this only happens from KDE's konsole or from xterm.
> aterm is OK as is a non-gui console.
>
> --
> gentoo-dev@gentoo.org mailing list
>
We are working on it, there is a bug on this.
Besides that, this is not the right list for your problems, bugzilla
would be a good start here. This list is for development related
discussion.
- foser
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-05-20 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 15:24 [gentoo-dev] Strange keymappings in nano Peter Ruskin
2003-05-20 15:30 ` Peter Ruskin
2003-05-20 17:53 ` foser [this message]
2003-05-20 16:41 ` Luke-Jr
2003-05-20 20:34 ` Kumba
2003-05-20 21:48 ` Peter Ruskin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1053453228.8442.1.camel@rivendell \
--to=foser@foser.dyn.warande.net \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox