> On Fri, 28 Mar 1997, Pete Harlan wrote:
>
> > In bash it's ^R for reverse, and ^S for forward search, just like in
> > emacs. Perhaps if you select vi rules for bash it will use whatever
> > horror vi uses for searching.
> >
> ^S only freezes my xterm and i have to press ^Q to make it work agai
> Kai Grossjohann writes:
Kai> The function history-search-backward which I bound to M-p does exactly
Kai> this. (Similar for M-n, history-search-forward.)
I must have been out of my mind :-(
Sorry, of course the Bash 1.X history-search-{for,back}ward don't do
this right.
kai
--
A lar
> Gertjan Klein writes:
Gertjan> [...] The principle is this: if you have an empty
Gertjan> commandline and you type the up arrow, you get the previous
Gertjan> command. If you've already typed something, you get
Gertjan> whatever previous command starts with that. This combines
Ge
I thought it worthwhile to send this again with a Subject that might
attract the attention of more people.
> > > >> Open up your info reader;
> > > Gertjan> Don't get me started on info!
> > > Why not? Elucidate.
> > I think info sucks. It is obsoleted by html. Clear enough?
>
> Same
On Wed, 2 Apr 1997, Hamish Moffatt wrote:
> > > >> Open up your info reader;
> > > Gertjan> Don't get me started on info!
> > > Why not? Elucidate.
> > I think info sucks. It is obsoleted by html. Clear enough?
>
> Same story here. The gnu info browser is too obscure, if you're
> not
-BEGIN PGP SIGNED MESSAGE-
On 02-Apr-97 Hamish Moffatt wrote:
>On Tue, Apr 01, 1997 at 10:24:30PM +0200, J.P.D. Kooij wrote:
>> On Mon, 31 Mar 1997, Karl M. Hegbloom wrote:
>> > > "Gertjan" == Gertjan Klein <[EMAIL PROTECTED]> writes:
>> > Gertjan> "Karl M. Hegbloom" <[EMAIL PROTE
On Tue, Apr 01, 1997 at 10:24:30PM +0200, J.P.D. Kooij wrote:
> On Mon, 31 Mar 1997, Karl M. Hegbloom wrote:
> > > "Gertjan" == Gertjan Klein <[EMAIL PROTECTED]> writes:
> > Gertjan> "Karl M. Hegbloom" <[EMAIL PROTECTED]> wrote:
> > >> Open up your info reader;
> > Gertjan> Don't
On Mon, 31 Mar 1997, Karl M. Hegbloom wrote:
> > "Gertjan" == Gertjan Klein <[EMAIL PROTECTED]> writes:
>
> Gertjan> "Karl M. Hegbloom" <[EMAIL PROTECTED]> wrote:
> >> Open up your info reader;
>
> Gertjan> Don't get me started on info!
>
> Why not? Elucidate.
I think inf
On Mar 31, Gertjan Klein wrote
> > If you type, say, "g" then M-p repeatedly you get
> > all command lines that begin with "g". I use this *all* the time, as
> > an alternative to "!g" because it lets me see if I got the right
> > command line before I hit Enter.
>
> Still, none of this eve
> Do you mean that they fixed libreadline so that you can now talk about
> the 'up' key instead of having to insert escape sequences? That's be
> great... IMHO, it's probably libreadline's biggest problem.
I do not know about this. What I meant was that they fixed
history-search-backward.
--
M
> "James" == James Troup <[EMAIL PROTECTED]> writes:
James> "Karl M. Hegbloom" <[EMAIL PROTECTED]> writes:
>> > > Open up your info reader; > > Don't get me started on info!
>>
>> Why not? Elucidate. (I imagine it will have to do with 'C-n
>> and C-p rather than arrow ke
"Karl M. Hegbloom" <[EMAIL PROTECTED]> writes:
> > > Open up your info reader;
> >
> > Don't get me started on info!
>
> Why not? Elucidate. (I imagine it will have to do with 'C-n and
> C-p rather than arrow keys' type of things... If you use Emacs,
> that's fixed, and arrow keys work fine.)
> "Gertjan" == Gertjan Klein <[EMAIL PROTECTED]> writes:
Gertjan> "Karl M. Hegbloom" <[EMAIL PROTECTED]> wrote:
>> Open up your info reader;
Gertjan> Don't get me started on info!
Why not? Elucidate. (I imagine it will have to do with 'C-n and
C-p rather than arrow keys' ty
"Karl M. Hegbloom" <[EMAIL PROTECTED]> wrote:
> Open up your info reader;
Don't get me started on info!
> and read the 'readline'
> manual, which you've obviously not heard of yet...
? I see no reason in my post for you to make such an assumption.
> And here's a copy of the ~/.input
Michel Beland <[EMAIL PROTECTED]> wrote:
> Second, if you have not already typed something on the command line,
> history-search-backward does not match any previous command in the
> history and just beeps. 4DOS and tcsh just match all the commands
> instead and show you the first match.
B
On Mar 30, Michel Beland wrote
>
[snip]
>
> In bash, write
>
> "\e[A":history-search-backward
> "\e[B":history-search-forward
>
> in your ~/.inputrc file. There are two problems with bash, though.
> First, if you log on your linux machine with a terminal that does not
> use ESC [ A for the up a
> Still, none of this even begins to compare with the ease of use of
> (horror! shock!) the DOS command interpreter 4DOS! Why use separate
> keys like M-p for this, when you've got the arrow keys? The principle
> is this: if you have an empty commandline and you type the up arrow, you
> get the
> "Gertjan" == Gertjan Klein <[EMAIL PROTECTED]> writes:
Gertjan> I wish I could convince bash to work like this!
Open up your info reader; either inside Emacs or XEmacs, by typing
'info' at a bash prompt, or via http and dwww, and read the 'readline'
manual, which you've obviously not h
Kai Grossjohann <[EMAIL PROTECTED]> wrote:
> If you type, say, "g" then M-p repeatedly you get
> all command lines that begin with "g". I use this *all* the time, as
> an alternative to "!g" because it lets me see if I got the right
> command line before I hit Enter.
Still, none of this ev
On Fri, 28 Mar 1997, Pete Harlan wrote:
> In bash it's ^R for reverse, and ^S for forward search, just like in
> emacs. Perhaps if you select vi rules for bash it will use whatever
> horror vi uses for searching.
>
^S only freezes my xterm and i have to press ^Q to make it work again.
How come yo
> Pete Harlan writes:
Kai> ,-
Kai> | M-p: history-search-backward
Kai> | M-n: history-search-forward
Kai> `-
Pete> In bash it's ^R for reverse, and ^S for forward search, just
Pete> like in emacs. Perhaps if you select vi rules for bash it
Pete> will use whatever horror
> Alex> - In tcsh I can type anything on the command line and do a
> Alex> search on the history list matching this input by pressing
> Alex> ALT-P. How do I do that with bash?
>
> I also came from tcsh, therefore I put this in my ~/.inputrc and I'm
> happy ever since 8-)
>
> ,-
> | M-p
> Alexander Lazarevic writes:
Alex> - In tcsh I can type anything on the command line and do a
Alex> search on the history list matching this input by pressing
Alex> ALT-P. How do I do that with bash?
I also came from tcsh, therefore I put this in my ~/.inputrc and I'm
happy ever since
Jean Pierre LeJacq <[EMAIL PROTECTED]> writes:
>This will strip the shortest suffix that matches ".*"
>
> ${var%.*}
>
>This will strip the longest suffix that matches ".*"
>
> ${var%.*}
Oops. ${var%%.*} strips the longest. And using # instead of % will
strip from the begi
On Sat, 22 Mar 1997, Alexander Lazarevic wrote:
> - In a tcsh I can do $var:r, which gives me 'name' if $var contaned
> 'name.ext'. How can I do this with bash?
This will strip the shortest suffix that matches ".*"
${var%.*}
This will strip the longest suffix that matches ".*"
I've read the man page on bash several times now, but I can't find out
how to get the following to work:
- In a tcsh I can do $var:r, which gives me 'name' if $var contaned
'name.ext'. How can I do this with bash?
- In tcsh I can type anything on the command line and do a search on the
history l
26 matches
Mail list logo
