Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15666
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: [readline] Multibyte invisible chars cause weird prompt length calculation issue |
| Date | 2019-11-27 20:29 -0500 |
| Organization | ITS, Case Western Reserve University |
| Message-ID | <mailman.2953.1574905401.13325.bug-bash@gnu.org> (permalink) |
| References | (1 earlier) <68c76159-3cf3-b12f-9145-f0578d5415a3@case.edu> <db11c81c9312dec35fa6579db44dc03d03bb27fd.camel@mail.ru> <f7cb9c63-1eeb-89c0-2bb7-439794075279@case.edu> <f2e0255652f53d22135229ed61f27cca00a312fe.camel@mail.ru> <2f0b7923-3b8b-f16c-f35f-f4c8c6782161@case.edu> |
On 11/27/19 3:19 PM, Алексей Шилин wrote: > В Ср, 27/11/2019 в 11:48 -0500, Chet Ramey пишет: >> The reason I ask is that I can (unsurprisingly) reproduce multiple >> redisplay issues if the newline after the `\h:' is present, but none >> when $PS1 doesn't contain any newlines. > > You mean you can't reproduce the issue? That's weird, since I can > easily do it in Konsole, in GNOME Terminal, even in bare tty; in Debian > 10, in Fedora 31 - all with PS1 as simple as '\[\e]0;\w\a\]\w\$ '. Are > you sure you're using a multi-byte path (like the one I provided) and a > *.UTF-8 locale? Yes, and yes. I poked around enough and found the cause. There will be a fix in the next devel branch push. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: [readline] Multibyte invisible chars cause weird prompt length calculation issue Chet Ramey <chet.ramey@case.edu> - 2019-11-27 20:29 -0500
csiph-web