Re: Multi-word matching in history expansion

2007-09-30 Thread Bob Proulx
The Wanderer wrote: > Quite some time and several varyingly-significant updates of bash > ago, I was able to perform history expansion on multi-word commands. > > At present and for some while now, it instead expands to > > ls /tmp/ /h This is also what csh does in this situation too. This type

Re: Multi-word matching in history expansion

2007-09-30 Thread Paul Jarc
The Wanderer <[EMAIL PROTECTED]> wrote: > !ls /h How about: ls /h paul

Multi-word matching in history expansion

2007-09-30 Thread The Wanderer
I'm not entirely sure that this is the appropriate forum for this kind of question, since the issue at hand does not seem to be in any respect a bug, but I haven't found any better one; if there's something I've missed, please let me know. I am presently running bash 3.1.17, obtained via Debian.

Re: How to include `$$' literally in the PS1 prompt?

2007-09-30 Thread Andreas Schwab
"Clark J. Wang" <[EMAIL PROTECTED]> writes: > Anybody has any idea? PS1='[\\$\\$=$$ \w] \$ ' Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And

How to include `$$' literally in the PS1 prompt?

2007-09-30 Thread Clark J. Wang
I want to show the bash PID in my prompt. For example, if the PID of shell is 12345 I want the prompt to look like this: [$$=12345 ~/tmp] # If I set PS1 like this: PS1='[$$=$$ \w] \$ ' then both `$$' would be expanded to 12345. If I set PS1 like this: PS1='[\$\$=$$ \w] \$ ' then `\$\$' would