Using C-s to forward search command history

Using C-s to forward search command history

[Greg Law]

Hi group,

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 :-(

Have I misunderstood, or is there a way round this?  (It would be very 
useful for me to be able to search forwards).


Thanks in advance,

Greg

Re: Using C-s to forward search command history

[Bob Rossi]

> 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 :-(
> 
> Have I misunderstood, or is there a way round this?  (It would be very 
> useful for me to be able to search forwards).

This is not a GDB issue, it's a readline issue. Try doing the same thing
with while using the bash shell. You might be able to remap the
functionality of forward-search-history in your .inputrc. 

Bob Rossi

Re: Using C-s to forward search command history

[Michael Veksler]

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 :-(
>
> Have I misunderstood, or is there a way round this?  (It would be very
> useful for me to be able to search forwards).

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

Re: Using C-s to forward search command history

[Bob Rossi]

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 :-(
> >
> > Have I misunderstood, or is there a way round this?  (It would be very
> > useful for me to be able to search forwards).
> 
> 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?

Bob Rossi

Re: Using C-s to forward search command history

[Michael Veksler]

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

Re: Using C-s to forward search command history

[Andreas Schwab]

Michael Veksler <VEKSLER@il.ibm.com> writes:

> 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.

IMHO readline should be built with USE_XON_XOFF, so that you can have
both.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: Using C-s to forward search command history

[Dan Kegel]

Bob Rossi wrote:
>>This is a terminal feature that interferes with your C-s use,
>>it is not a readline issue.

Bzzt.  Programs that want to accept commands like control-s
are supposed to put the terminal into raw mode.  The
readline library does this.  If it didn't work,
something's wrong.

> That's interesting. Is the (stop/start) ^s/^q feature of the terminal
> even useful these days? Why is it defaulted on?

Yes, it's useful.  I use it every other day or so when
a program is spewing lots of output; I hit ^s, then
I can scroll back without having it scroll to the
end every time the program outputs something else.
- Dan

-- 
Trying to get a job as a c++ developer?  See http://kegel.com/academy/getting-hired.html