Re: Prompt issue within cygwin

2006-02-08 Thread Eric Blake
According to Zach Gelnett on 2/6/2006 7:55 AM: >>Chet Ramey, the upstream readline maintainer, FINALLY admitted that his >>routines have display bugs when readline is compiled with multi-byte >>support, and when a single-line prompt contains invisible characters. > Interesting, so, based on my rea

Re: Prompt issue within cygwin

2006-02-06 Thread Zach Gelnett
>Chet Ramey, the upstream readline maintainer, FINALLY admitted that his >routines have display bugs when readline is compiled with multi-byte >support, and when a single-line prompt contains invisible characters. The >problem stems from the fact that there is no reliable way to determine >which c

Re: Prompt issue within cygwin

2006-02-06 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 1/24/2006 7:12 AM: > > Shoot - the bug is still not fixed upstream; I reproduced it with > bash-3.1-1, readline-5.1-1, and rxvt-2.7.10-6. One of these days, I hope > to be able to sit down and figure out where readline is

Re: Prompt issue within cygwin

2006-01-24 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Igor Peshansky on 1/23/2006 4:18 PM: >>I'm trying to get this prompt to work: >> >>PS1="\[\033]61;[EMAIL PROTECTED]@\H \W>" >> >>but the issue there is that the > is duplicated (just like the space >>above, but much more noticable). Any i

Re: Prompt issue within cygwin

2006-01-23 Thread Brian Dessent
Igor Peshansky wrote: > There is a prompt bug in bash that causes it to miscount the number of > displayed characters. One workaround was to append '\[\]' to PS1. Also, > a good habit to get into is to use single quotes in the shell when some > value contains backslashes. Yes, this bug has been

Re: Prompt issue within cygwin

2006-01-23 Thread Igor Peshansky
On Mon, 23 Jan 2006, Zach Gelnett wrote: > On 1/23/06, Zach Gelnett <[EMAIL PROTECTED]> wrote: > > On 1/23/06, Igor Peshansky <[EMAIL PROTECTED]> wrote: Again, . Let's not feed the spammers. > [snip] > I do have one final question. > > If I set PS1 lik

Re: Prompt issue within cygwin

2006-01-23 Thread Zach Gelnett
On 1/23/06, Zach Gelnett <[EMAIL PROTECTED]> wrote: > pls see: > > http://materm.sourceforge.net/docs/settitle.c > > On 1/23/06, Igor Peshansky <[EMAIL PROTECTED]> wrote: > > Ugh, top-posting... Reformatted. > > > > Two more notes: first, the Cygwin lists don't accept HTML email, as you no > > dou

Re: Prompt issue within cygwin

2006-01-23 Thread Zach Gelnett
pls see: http://materm.sourceforge.net/docs/settitle.c On 1/23/06, Igor Peshansky <[EMAIL PROTECTED]> wrote: > Ugh, top-posting... Reformatted. > > Two more notes: first, the Cygwin lists don't accept HTML email, as you no > doubt found out from the rejection notice, and second, please make sure

Re: Prompt issue within cygwin

2006-01-23 Thread Igor Peshansky
Ugh, top-posting... Reformatted. Two more notes: first, the Cygwin lists don't accept HTML email, as you no doubt found out from the rejection notice, and second, please make sure your mailer respects the Reply-To: header -- I set it for a reason. On Mon, 23 Jan 2006, Zach Gelnett wrote: > On 1

Re: Prompt issue within cygwin

2006-01-23 Thread Igor Peshansky
On Mon, 23 Jan 2006, Eric Blake wrote: > > > \[\033]61;[EMAIL PROTECTED]@\H \W> > > > > > > as you can see, only a single ">" > > > [snip] > > > > You have a bug in your PS1 value. Bash uses \[ and \] to delimit > > non-printable sequences in the prompt. So, your PS1 should at least be > > > > \

Re: Prompt issue within cygwin

2006-01-23 Thread Eric Blake
> > > > \[\033]61;[EMAIL PROTECTED]@\H \W> > > > > as you can see, only a single ">" > > [snip] > > You have a bug in your PS1 value. Bash uses \[ and \] to delimit > non-printable sequences in the prompt. So, your PS1 should at least be > > \[\033]61;[EMAIL PROTECTED]@\H \W> >

Re: Prompt issue within cygwin

2006-01-23 Thread Igor Peshansky
Ugh, top-posting... Reformatted. On Mon, 23 Jan 2006, Zach Gelnett wrote: > On 1/23/06, Igor Peshansky <[EMAIL PROTECTED]> wrote: . Thanks. > > On Mon, 23 Jan 2006, Zach Gelnett wrote: > > > > > Here is what i am seeing: > > > > > > [EMAIL PROTECTED]

Re: Prompt issue within cygwin

2006-01-23 Thread Zach Gelnett
That was precicesly my issue. Thank you very much, both issues (tab complete and dup > entries) are resolved! FYI, I'm just trying to have a prompt that says: [EMAIL PROTECTED] workingdir> this is because i login to multiple machines and use tabbed windows (available within mrxvt) to do this.

Re: Prompt issue within cygwin

2006-01-23 Thread Igor Peshansky
On Mon, 23 Jan 2006, Zach Gelnett wrote: > Here is what i am seeing: > > [EMAIL PROTECTED] ~> > > > the duplicate ">" is the issue. Here is my PS1: > > \[\033]61;[EMAIL PROTECTED]@\H \W> > > as you can see, only a single ">" > [snip] You have a bug in your PS1 value. Bash uses \[ and \] to deli

Prompt issue within cygwin

2006-01-23 Thread Zach Gelnett
Here is what i am seeing: [EMAIL PROTECTED] ~> > the duplicate ">" is the issue. Here is my PS1: \[\033]61;[EMAIL PROTECTED]@\H \W> as you can see, only a single ">" This happens in xterm, cygwin bash shell, and my preferred terminal mrxvt (from materm.sf.net). It only just started happening