public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: 320095285153-0001@t-online.de (Achim Gottinger)
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Keyboard -- DEL Key
Date: Tue Feb  6 01:50:02 2001	[thread overview]
Message-ID: <3A7FB499.F6A6815@gottinger.de> (raw)
In-Reply-To: 20010206011948.A24074@cvs.gentoo.org

Pete Gavin wrote:

> On Tue, Feb 06, 2001 at 07:50:31AM +0100, Achim Gottinger wrote:
> > Knut Feiert wrote:
> >
> > > On Mon, 5 Feb 2001 11:49:54 -0700, Pete Gavin wrote:
> > >
> > > >
> > > >Add this line to your ~/.inputrc file to make the delete key work as
> > > >expected in bash:
> > > >
> > > >"\e[3~": delete-char
> > >
> > > Why is that? Oversight or feature?
> >
> > A point on my Todo list. Pete do you know which of the console-tools
> > files is the best place to start patching?
> >
> > achim~
> >
>
> This isn't anything that needs to be patched. Its actually a
> feature. Whenever you hit the delete key, it sends the sequence
> "\e[3~" (\e==^[), which the program can translate as it wishes. (The
> same sort of thing happens with the insert key, home and end, and page
> up/down.) The .inputrc file allows you to bind whatever keys to
> whatever functions you want. The bash developers just decided not to
> automatically bind delete to any function. If you want to make this
> automatic, you could add a .inputrc file containing that line to
> /etc/skel, so that every new user automatically has it in his/her home
> directory after its been created. Or, you could add this line to
> /etc/profile:
>
> bind '"\e[3~": delete-char'
>
> If you want more information on this stuff, do info bash and do a
> search on inputrc by hitting Ctrl-s.

Hmm ok it's a readline feature. Looks like /etc/inputrc should work too.
If not adding INPUTRC="/etc/inpurc" to /etc/profile should do the job.
At least I found such a file on a Suse6.3 system. I will add it to our
baselayout package.
Can you take a look at it. It seems you are more familary with it?

BTW I made a new gcc package that builds with or without libg++. I will
commit it with all the other sys-stuff
I did in about a day.

achim~

>
>
> Pete
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev




  reply	other threads:[~2001-02-06  8:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-06  0:07 [gentoo-dev] Keyboard -- DEL Key Knut Feiert
2001-02-06  0:17 ` Achim Gottinger
2001-02-06  1:20   ` Pete Gavin
2001-02-06  1:50     ` Achim Gottinger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-05 11:41 Knut Feiert
2001-02-05 11:50 ` Pete Gavin

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=3A7FB499.F6A6815@gottinger.de \
    --to=320095285153-0001@t-online.de \
    --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