public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: covici@ccs.covici.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Anyone else having a problem with bash?
Date: Sat, 11 Jul 2015 07:04:35 -0400	[thread overview]
Message-ID: <22156.1436612675@ccs.covici.com> (raw)
In-Reply-To: <slrnmq1bqc.dti.martin@lounge.imp.fu-berlin.de>

Martin Vaeth <martin@mvath.de> wrote:

> Nikos Chantziaras <realnc@gmail.com> wrote:
> > On 10/07/15 18:00, Gevisz wrote:
> >> bindkey '^[[7~' beginning-of-line                   # Home (xterm)
> >> bindkey '^[[8~'  end-of-line                        # End (xterm)
> >
> > lol... are these guys serious?
> >
> > It's 2015...
> 
> ... and yet the way of handling special keys in terminals has not
> changed: You cannot rely on any special sequence, since it depends
> on the terminal type (and changes also nowadays, depending on
> whether you use xterm, screen, tmux, linux console, ...).
> This is the reason why any fixed default can be wrong: What works in
> one terminal can break in another.
> The zsh way of doing this dynamically is much superior to the bash
> way of doing this statically in a fixed readline config file
> (which works only because *gentoo* provided a file which works
> for *most* linux terminals - I also had serious problems with bash
> and such keys when ssh-ing to e.g. sun stations; with zsh these
> problems are easily fixable).
> 
> One way to avoid the multiterm difficulty is to use the terminfo database
> of your current terminal. In zsh you do this as follows:
> 
> bindkey ${terminfo[khome]} beginning-of-line
> bindkey ${terminfo[kend]} end-of-line
> 
> (Yes, in zsh you usually do not have to quote variabeles!).
> 
> Note, however, that the above sets the keys only to your *current*
> terminal. If you call e.g. tmux later on and move your session to
> another terminal or you login from another terminal, you might again
> have problems, so it might be a good idea to set some sequences
> also for other terminals.
> 
> Again, I recommend you to use zshrc-mv from the mv overlay where
> all this (and much more) is done.
> 

hmmm, I am just trying zsh, and I still am having problems.  I cannot
see, so I use speakup or orca to read the screen to me and when I type
the second character of the command line, I hear the first character
again.  I am not sure what is happening, does the cursor move back a
character for a brief period, or what?  Also, the comp systemis very
confusing, its hard to read the list that is produced it seems to be in
columns of some sort and aside from just typing more characters on the
command line, I am not sure what to do.  I will look at your .zshrc, but
a lot of it will not do me any good, so I will read the docs and do
something.


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com


  reply	other threads:[~2015-07-11 11:04 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 17:01 [gentoo-user] Anyone else having a problem with bash? walt
2015-07-06 17:18 ` Alexander Kapshuk
2015-07-06 19:07   ` [gentoo-user] " »Q«
2015-07-06 20:43     ` Alex Thorne
2015-07-06 14:09       ` Bill Kenworthy
2015-07-08  4:44         ` Jc García
2015-07-08  5:00           ` Anton Shumskyi
2015-07-08  7:00             ` Alan McKinnon
2015-07-08  9:06               ` Florian Gamböck
2015-07-08  9:28                 ` Stephan Müller
2015-07-08 10:08                   ` Florian Gamböck
2015-07-08 10:13                     ` Joerg Schilling
2015-07-08 10:40                       ` Florian Gamböck
2015-07-08 10:53                         ` Joerg Schilling
2015-07-08  0:48   ` walt
2015-07-08  7:15     ` Florian Gamböck
2015-07-08 13:10       ` Todd Goodman
2015-07-08 13:46         ` Florian Gamböck
2015-07-08 10:17 ` Nikos Chantziaras
2015-07-08 10:29   ` Joerg Schilling
2015-07-09 11:38 ` [gentoo-user] " Stephan Müller
2015-07-09 11:48   ` Neil Bothwick
2015-07-09 12:01     ` Gevisz
2015-07-09 12:07       ` [gentoo-user] " Nikos Chantziaras
2015-07-09 12:20         ` Gevisz
2015-07-09 16:07         ` Neil Bothwick
2015-07-09 17:45           ` Gevisz
2015-07-09 17:54             ` Neil Bothwick
2015-07-09 23:34           ` Nikos Chantziaras
2015-07-09 23:36             ` Nikos Chantziaras
2015-07-09 23:54               ` wraeth
2015-07-10  5:29               ` Franz Fellner
2015-07-10  8:16               ` Neil Bothwick
2015-07-10 15:00                 ` Gevisz
2015-07-10 17:39                   ` Nikos Chantziaras
2015-07-10 22:18                     ` Marc Joliet
2015-07-11 10:22                       ` Nikos Chantziaras
2015-07-11 10:39                         ` Marc Joliet
2015-07-11 20:56                         ` Martin Vaeth
2015-07-12 16:52                           ` Nikos Chantziaras
2015-07-12 17:01                             ` Neil Bothwick
2015-07-12 22:35                               ` Martin Vaeth
2015-07-11  5:53                     ` Martin Vaeth
2015-07-11 11:04                       ` covici [this message]
2015-07-11 20:47                         ` Martin Vaeth
2015-07-13  9:21               ` Joerg Schilling
2015-07-13  9:30                 ` Peter Humphrey
2015-07-10  6:06             ` Martin Vaeth
2015-07-10  6:18           ` Martin Vaeth
2015-07-10  8:35             ` Neil Bothwick
2015-07-10 15:31               ` Martin Vaeth
2015-07-13  9:39                 ` Joerg Schilling
2015-07-13 14:00                   ` Martin Vaeth
2015-07-13 15:03                     ` Joerg Schilling
2015-07-13  9:27             ` Joerg Schilling
2015-07-13 13:55               ` Martin Vaeth
2015-07-13 14:40                 ` Joerg Schilling
2015-07-09 12:19     ` Nikos Chantziaras
2015-07-09 12:24       ` wraeth
2015-07-09 12:37         ` Nikos Chantziaras
2015-07-09 14:46           ` wraeth
2015-07-10 11:46           ` wraeth
2015-07-11 22:21             ` walt
2015-07-09 12:41     ` walt

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=22156.1436612675@ccs.covici.com \
    --to=covici@ccs.covici.com \
    --cc=gentoo-user@lists.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