Mail Archives: cygwin/2001/07/04/10:24:25
David,
Isn't _what_ a bug? I have no trouble with line wrap, including backspacing
from a wrapped line back to the line on which typing began. With or without
readline expansions having been applied.
I experience no troubles whatsoever, and have not since I got the prompt
strings worked out to properly use \[ ... \].
Randall
At 07:19 2001-07-04, David A. Cobb wrote:
>At 7/3/01 08:47 PM (Tuesday), Randall R Schulz wrote:
>>Hi,
>>
>>Here's a little more on the promt business. It has proved popular with
>>fellow nerds in my office:
>>
>>My PS1 for any terminal (emulator) that supports it (xterm, xterm-color,
>>vt100, vt102, vt220, cytwin, at least) is this:
>>
>>
>>PS1=$'\[\e]0; \u :: \W (\w)\a\]\!> '
>># Note:
>># This sequence:
>># ESC]0;
>># ^ zero
>># Starts the title setting sequence. Everything from there to
>># the CTRL-G (also "\a" within $'...') is put in the window title.
>># Some terminal emulators (notably TeraTerm) put a pretty stingy
>># limit on how much they'll display, but you don't have to limit
>># the length you attempt to put there
>
>Yes! Works as advertised and it's a thing of beauty.
>
>But isn't it still a bug in bash (or bash's in-built subset of readline)?
>
>
>>I don't mind the information typically put into prompts, but I _hate_ to
>>have it literally in the prompt!
>>
>>Randall
>
>David A. Cobb
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -