Re: 2 regressions related to PROMPT_COMMAND

2009-03-03 Thread Chet Ramey
smallnow wrote: > Configuration Information [Automatically generated, do not change]: > Machine: x86_64 > OS: linux-gnu > Compiler: gcc > Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' > -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu' > -DCONF_VENDOR='unknown' -

Re: 2 regressions related to PROMPT_COMMAND

2009-03-02 Thread Bob Proulx
Andreas Schwab wrote: > smallnow writes: > > PROMPT_COMMAND='$(cd)' > > Since $(cd) expands to nothing this is mostly a no-op. True. But he did say this as well: > > I used $(cd) as a trivial command substitution, but any command > > substitution seems to have the same effect. > > I actually ha

Re: 2 regressions related to PROMPT_COMMAND

2009-03-02 Thread Greg Wooledge
On Sun, Mar 01, 2009 at 10:29:00PM -0800, smallnow wrote: > Bug #1: > do: > PROMPT_COMMAND='$(cd)' I've never found any reasonable use for PROMPT_COMMAND. If you just want to perform command substitutions at prompt-writing time, use PS1: PS1='$(pwd)\$ ' Of course, this trivial example is more

Re: 2 regressions related to PROMPT_COMMAND

2009-03-02 Thread Andreas Schwab
smallnow writes: > Bug #1: > do: > PROMPT_COMMAND='$(cd)' Since $(cd) expands to nothing this is mostly a no-op. Andreas. -- Andreas Schwab, sch...@linux-m68k.org Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."