yeah - the issue on my system was that I was not using the start-of and end-of
color characters properly - for example:
= ORIGINAL PS1 STRING =
export PS1="[\e[1;36m\w @ \h\e[m] \n[\e[1;35m\t \u\e[m] > "
= NEW PS1 STRING =
export PS1="[\[\033[1;36m\]\w @ \h\[\033[0m]\n\][\[\033[
> This ever get solved? I had the same issue in bash v3.2x and the root cause
> was the formatting.
If it's the one I'm thinking of, nobody was ever able to reproduce it.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
Chet Ramey, ITS, CWRUc...@case.eduhttp://tisw
This ever get solved? I had the same issue in bash v3.2x and the root cause
was the formatting.
Let me know if you want more info - Thanks.
--
Glad I'm not alone here!
BTW patching to 4.0.17 did nothing to fix the problem
Ian Kelling wrote:
> Chet Ramey wrote:
> > Ian Kelling wrote:
> >> Special Sauce wrote:
> >>> From: anton
> >>> To: bug-bash@gnu.org
> >>> Subject: Cursor starts inside prompt
> >> I just noticed this issue too. It see
Chet Ramey wrote:
Ian Kelling wrote:
Special Sauce wrote:
From: anton
To: bug-bash@gnu.org
Subject: Cursor starts inside prompt
I just noticed this issue too. It seems it was fine under gnu screen,
but not with plain xterm or gnome-terminal. Upgrading to the latest
patch version 4.0.17 fixed i
Chet Ramey wrote:
> Ian Kelling wrote:
>> Special Sauce wrote:
>>> From: anton
>>> To: bug-bash@gnu.org
>>> Subject: Cursor starts inside prompt
>> I just noticed this issue too. It seems it was fine under gnu screen,
>> but not with plain xterm or gnome-terminal. Upgrading to the latest
>> patch
Ian Kelling wrote:
> Special Sauce wrote:
>> From: anton
>> To: bug-bash@gnu.org
>> Subject: Cursor starts inside prompt
>
> I just noticed this issue too. It seems it was fine under gnu screen,
> but not with plain xterm or gnome-terminal. Upgrading to the latest
> patch version 4.0.17 fixed it.
Special Sauce wrote:
From: anton
To: bug-bash@gnu.org
Subject: Cursor starts inside prompt
I just noticed this issue too. It seems it was fine under gnu screen, but not
with plain xterm or gnome-terminal. Upgrading to the latest patch version
4.0.17 fixed it.
- Ian Kelling
On Apr 8, 4:42 pm, Mike Frysinger wrote:
> On Wednesday 08 April 2009 10:49:06 Special Sauce wrote:
>
> > On Apr 8, 1:52 am, Mike Frysinger wrote:
> > > and what `locale` settings you're using
>
> > @Mike What do you mean by locale?
>
> run `locale` and post the output
> -mike
>
> signature.asc
On Wednesday 08 April 2009 10:49:06 Special Sauce wrote:
> On Apr 8, 1:52 am, Mike Frysinger wrote:
> > and what `locale` settings you're using
>
> @Mike What do you mean by locale?
run `locale` and post the output
-mike
signature.asc
Description: This is a digitally signed message part.
On Apr 8, 1:52 am, Mike Frysinger wrote:
> and what `locale` settings you're using
> -mike
>
> signature.asc
> < 1KViewDownload
@Mike What do you mean by locale?
On Apr 8, 7:16 am, Greg Wooledge wrote:
> On Tue, Apr 07, 2009 at 11:04:58PM -0700, Special Sauce wrote:
>
> > [an...@nobby-nobbs ~]$ echo $PS1
> > [\[\e[28;1m\...@\h\[ \e[0m\]\w]$
>
> ^^^
> The space after \[ is not correct. You're sending a space to the terminal
> (or possib
On Apr 8, 7:16 am, Greg Wooledge wrote:
> On Tue, Apr 07, 2009 at 11:04:58PM -0700, Special Sauce wrote:
>
> > [an...@nobby-nobbs ~]$ echo $PS1
> > [\[\e[28;1m\...@\h\[ \e[0m\]\w]$
>
> ^^^
> The space after \[ is not correct. You're sending a space to the terminal
> (or possib
On Tue, Apr 07, 2009 at 11:04:58PM -0700, Special Sauce wrote:
>
> [an...@nobby-nobbs ~]$ echo $PS1
> [\[\e[28;1m\...@\h\[ \e[0m\]\w]$
^^^
The space after \[ is not correct. You're sending a space to the terminal
(or possibly more than one space -- since you didn't quote "$PS1
and what `locale` settings you're using
-mike
signature.asc
Description: This is a digitally signed message part.
Special Sauce wrote:
[an...@nobby-nobbs ~]$ echo $PS1
[\[\e[28;1m\...@\h\[ \e[0m\]\w]$
[an...@nobby-nobbs ~]$ echo $PS2
Work fine with the bash in the ubuntu repos
I put this at the end of my .bashrc and it works fine for me.
PS1='[\[\e[28;1m\...@\h\[ \e[0m\]\w]$ '
Theres probably something e
Mike Frysinger wrote:
considering it seems to involve the prompt, you really need to post your exact
prompt settings (i.e. PS1/PS2/etc...)
-mike
Realize that in PS vars, \[ and \] should be used around non-printable
characters. This surely won't happen if you start with --norc. You've got to
On Apr 8, 12:08 am, Mike Frysinger wrote:
> On Tuesday 07 April 2009 15:10:16 Special Sauce wrote:
>
>
>
> > From: anton
> > To: bug-b...@gnu.org
> > Subject: Cursor starts inside prompt
>
> > Configuration Information [Automatically generated, do not change]:
> > Machine: x86_64
> > OS: linux-gnu
On Tuesday 07 April 2009 15:10:16 Special Sauce wrote:
> From: anton
> To: bug-bash@gnu.org
> Subject: Cursor starts inside prompt
>
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF
From: anton
To: bug-bash@gnu.org
Subject: Cursor starts inside prompt
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-un
20 matches
Mail list logo
