[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Command prompt disappears when working directory is one whose name e
From: |
Chet Ramey |
Subject: |
Re: Command prompt disappears when working directory is one whose name ends in a '\' (backslash) |
Date: |
Sat, 15 Nov 2008 18:14:49 -0500 |
User-agent: |
Thunderbird 2.0.0.17 (Macintosh/20080914) |
Jonathan Plafker wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i486
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
> -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL
> -DHAVE_CONFIG_H -I. -I../bash -I../bash/include -I../bash/lib -g -O2
> -Wall
> uname output: Linux hp-ubuntu 2.6.24-18-generic #1 SMP Wed May 28 20:27:26
> UTC 2008 i686 GNU/Linux
> Machine Type: i486-pc-linux-gnu
>
> Bash Version: 3.2
> Patch Level: 39
> Release Status: release
>
> Description:
> Command prompt disappears when working directory is one whose name ends
> in a '\' (backslash)
> Repeat-By:
> Running the following command:
> mkdir ./asdf\\ && cd ./asdf\\
> Fix:
> Probably has something to do with the way things are escaped in the
> default $PS1.
> Mine is '${debian_chroot:+($debian_chroot)}\u@\h:\w\$' (without quotes),
> and I haven't changed it, so I assume its the default.
This has come up before. I suspect you have something in PROMPT_COMMAND
that tries to write to an xterm title bar and is confused by the backslash
at the end of $PWD.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/