Re: truncating the path in the bash prompt?

2009-01-13 Thread Dan Nicolaescu
Dan Nicolaescu writes: > In tcsh %c can be used to only show the last few directory names in a > path (also see the ellipsis variable). > > For example for this directory: > > /lib/modules/2.6.21-1.3194.fc7/kernel/drivers/char/hw_random/ > > the prompt can look like this:

Re: run-fg-editor for bash?

2009-01-13 Thread Dan Nicolaescu
Dan Nicolaescu writes: > In tcsh the command run-fg-editor bound by default to C-M-z is > extremely useful when you have an editor suspended. > It makes it very easy to return to the editor, do some editing, then > suspend the editor again, and the command line is restored in exactly >

coprocess suggestions

2009-01-13 Thread Pierre Gaston
I have a couple of suggestions about coprocesses. If I understood correctly how coproc works, I think that instead of : coproc [NAME] command [redirections] the documentation would be a little clearer with something like: coproc simple-command [redirections] coproc NAME compound-command [redirec

Re: execution hook

2009-01-13 Thread Bob Proulx
eneville_ wrote: > Bob Proulx wrote: > > Look at the documentation for BASH_ENV in the bash manual. > > Thanks. But this isn't having the effect that I wished for. > > What I'm hoping to achieve is to have bash run something like a wrapper > around each and every command line that I run. > > For

Re: Testing Bash 4.0

2009-01-13 Thread Chet Ramey
> 2 when running scripts the script works, but get constant output of > TRACE: pid 7958: parse_and_execute: turned on CMD_IGNORE_RETURN from > comsub_ignore_return > TRACE: pid 7964: parse_and_execute: turned on CMD_IGNORE_RETURN from > comsub_ignore_return > TRACE: pid 7968: parse_and_execute:

Testing Bash 4.0

2009-01-13 Thread Jim Gifford
2 Issues 1 configure script is not executable. Just had to chmod +x configure 2 when running scripts the script works, but get constant output of TRACE: pid 7958: parse_and_execute: turned on CMD_IGNORE_RETURN from comsub_ignore_return TRACE: pid 7964: parse_and_execute: turned on CMD_IGNORE_R

Re: Quick question: mv !(file) !$

2009-01-13 Thread Chet Ramey
Yang Zhang wrote: > So it's failing on the first bang? But there is no problem once I > replace !$ with 'dhclient' - usually extglob seems to work fine with the > suppression of history expansion. Or does the presence of !$ somehow > trigger history expansion (normally not run) which then attemp

Re: execution hook

2009-01-13 Thread Chet Ramey
> I was looking for a way to run a program prior to bash executing the > program. Does anyone know of a hook that can do this, such as an environment > that hold this hook value. The closest you're going to be able to get is the DEBUG trap. Chet -- ``The lyf so short, the craft so long to lerne

Re: execution hook

2009-01-13 Thread eneville_
Bob Proulx wrote: > > eneville_ wrote: >> I was looking for a way to run a program prior to bash executing the >> program. Does anyone know of a hook that can do this, such as an >> environment >> that hold this hook value. > > Look at the documentation for BASH_ENV in the bash manual. > >

Re: Quick question: mv !(file) !$

2009-01-13 Thread Yang Zhang
Chet Ramey wrote: Yang Zhang wrote: Hi, why doesn't the second command work? (Trying to move all files into a newly created directory.) $ mkdir dhclient $ mv !(dhclient) !$ bash: !: event not found It doesn't work because enabling the `extglob' option doesn't cause bash to tell the history l