public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Michael Veksler <VEKSLER@il.ibm.com>
To: Bob Rossi <bob@brasko.net>
Cc: gdb@sources.redhat.com, Greg Law <greg@greglaw.net>,
	Julian Smith <jules@op59.net>
Subject: Re: Using C-s to forward search command history
Date: Sat, 20 Aug 2005 16:05:00 -0000	[thread overview]
Message-ID: <OF3FA71C36.9FB334B3-ONC2257063.005820B4-C2257063.0058819B@il.ibm.com> (raw)
In-Reply-To: <20050820132023.GA20235@white>





Bob Rossi <bob@brasko.net> wrote on 20/08/2005 16:20:23:
> On Sat, Aug 20, 2005 at 03:19:33PM +0300, Michael Veksler wrote:
> >
> > Greg Law  wrote on 19/08/2005 16:12:43:
> > > If I've read the info pages correctly, I can use C-s in order to
search
> > > the command history forwards.  However, this sequence also seems to
be
> > > the control sequence to suspend the terminal :-(
[...]
> >
> > This is a terminal feature that interferes with your C-s use,
> > it is not a readline issue. The following line works for me.
> > I put it in my .kshrc, .cshrc, .zshrc startup files after
> > making sure this is an interactive shell:
> >       stty -ixon
>
> That's interesting. Is the (stop/start) ^s/^q feature of the terminal
> even useful these days? Why is it defaulted on?

I see people use the ^s/^q all the time, especially with a long running
application that emits a line of trace about every second.
I like the search feature more, so I disable the suspend sequence.

  Michael

  reply	other threads:[~2005-08-20 16:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-19 13:12 Greg Law
2005-08-19 13:31 ` Bob Rossi
2005-08-20 12:18 ` Michael Veksler
2005-08-20 13:20   ` Bob Rossi
2005-08-20 16:05     ` Michael Veksler [this message]
2005-08-20 17:23       ` Andreas Schwab
2005-08-20 17:55     ` Dan Kegel

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=OF3FA71C36.9FB334B3-ONC2257063.005820B4-C2257063.0058819B@il.ibm.com \
    --to=veksler@il.ibm.com \
    --cc=bob@brasko.net \
    --cc=gdb@sources.redhat.com \
    --cc=greg@greglaw.net \
    --cc=jules@op59.net \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).