inconsistent output for cd

2007-04-02 Thread Tony Balinski
Configuration Information [Automatically generated, do not change]: Machine: i686 OS: cygwin Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='i686-pc-cygwin' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -D

Re: how does bash parse back-ticks, anyway?

2007-04-02 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Matthew Woehlke on 4/2/2007 5:09 PM: >> Matthew, it's not a bug in bash, it's a feature. $(foo) and `foo` >> are not 100% equivalent. Read the command substitution paragraph >> in the bash man page. > > I did, and I saw that it talked abo

Re: [Bug 103756] kate: syntax highlighting error: bash and escaped quotes

2007-04-02 Thread Matthew Woehlke
Eric Blake-1 wrote: Current bash.xml accepts (a), but not (b). The single qoute is the start of string highlight. It's also not just the backtick block, but the backtick block inside of a double quote string block - and vice versa. First, be aware that `` in bash 3.1 was buggy, so you should up

Re: [Bug 103756] kate: syntax highlighting error: bash and escaped quotes

2007-04-02 Thread Eric Blake-1
> > Current bash.xml accepts (a), but not (b). The single qoute is > > the start of string highlight. It's also not just the backtick > > block, but the backtick block inside of a double quote string > > block - and vice versa. First, be aware that `` in bash 3.1 was buggy, so you should upgrade

Re: how does bash parse back-ticks, anyway? (was: [Bug 103756] kate: syntax highlighting error: bash and escaped quotes)

2007-04-02 Thread Matthew Woehlke
Since this is not really appropriate to the bug report, I am moving it exclusively to the lists. Please direct replies to kwrite-develkde.org and bug-bashgnu.org. Carsten Lohrke wrote: Matthew Woehlke wrote: Carsten Lohrke wrote: Current bash.xml accepts (a), but not (b). The single qoute is

Re: [Bug 103756] kate: syntax highlighting error: bash and escaped quotes

2007-04-02 Thread Matthew Woehlke
Carsten Lohrke wrote: Current bash.xml accepts (a), but not (b). The single qoute is the start of string highlight. It's also not just the backtick block, but the backtick block inside of a double quote string block - and vice versa. x="`echo \"'\\\"\"`"is valid My bash highlighter thinks

Re: shouldn't prompt printing be smarter?

2007-04-02 Thread Thomas Dickey
Chet Ramey <[EMAIL PROTECTED]> wrote: > Fran Litterio wrote: >>> Also, creating an "option" to decide which behaviour should be followed >>> (current one or the one I propose) would make everyone happy >> >> It should be possible to code a value for PROMPT_COMMAND that sends >> the cursor position