Re: shell prompt undesired characters

[Peter Dyballa <Peter_Dyballa@web.de>]

Am 08.04.2009 um 19:53 schrieb Dan Davison:

> I've tried without any
> ~/.emacs

I mentioned ~/.emacs_bash – it only customises bash when run inside  
*shell* buffer. And this file is more useful than a car because it  
can switch off so many things that are fine in a (dumb) terminal  
emulation which GNU Emacs can do better.

> and ~/.bashrc, on emacs22, and I still get those initial
> characters.

Bash uses much more files, see 'man bash' or other bash documentation  
(obviously there are good reasons why I don't use bash by default).

> They're not coming from $PS1, so where are they coming from?


Can you also check the meaning of PS1 in GNU Emacs's *shell* buffer?  
In a terminal I have

	PS1='\e[34;47;1m\j-\[\033[0;32m\]ttyp\[\033[0;31m\]://\[\033[0;32m\] 
pete\[\033[0;31m\]:5\[\033[0;34m\]${PWD/$HOME//~pete}\e[33;46;1m \! /\ 
\ \[\033[0m\]'

in *shell* buffer it's

	PS1='\h:\w \u\$ '

Thanks to ~/.emacs_bash, which does not contain ELisp but shell code:

	PATH=$(defaults read "${HOME}/.MacOSX/environment" PATH)
	MANPATH=$(defaults read "${HOME}/.MacOSX/environment" MANPATH)
	PS1='\h:\w \u\$ '
	unset DYLD_LIBRARY_PATH
	BASH_ENV=${HOME}/Library/init/bash/aliases.mine

--
Greetings

   Pete

They that can give up essential liberty to obtain a little temporary  
safety deserve neither liberty nor safety.
		-Benjamin Franklin, Historical Review of Pennsylvania.