Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: =?koi8-r?Q?=E1=CC=C5=CB=D3=C5=CA_?= =?koi8-r?Q?=FB=C9=CC=C9=CE?= <rootlexx@mail.ru>
Newsgroups: gnu.bash.bug
Subject: Re: [readline] Multibyte invisible chars cause weird prompt length calculation issue
Date: Wed, 27 Nov 2019 23:19:14 +0300
Lines: 12
Approved: bug-bash@gnu.org
Message-ID: <mailman.2918.1574885967.13325.bug-bash@gnu.org>
References: <3dd641953467a3299265e479026fc40a7bb697d4.camel@mail.ru> <68c76159-3cf3-b12f-9145-f0578d5415a3@case.edu> <db11c81c9312dec35fa6579db44dc03d03bb27fd.camel@mail.ru> <f7cb9c63-1eeb-89c0-2bb7-439794075279@case.edu> <f2e0255652f53d22135229ed61f27cca00a312fe.camel@mail.ru>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Trace: usenet.stanford.edu 1574885968 11821 209.51.188.17 (27 Nov 2019 20:19:28 GMT)
X-Complaints-To: action@cs.stanford.edu
To: chet.ramey@case.edu, bug-bash@gnu.org
Envelope-to: bug-bash@gnu.org
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2; h=Content-Transfer-Encoding:MIME-Version:Content-Type:References:In-Reply-To:Date:To:From:Subject:Message-ID; bh=n7FVTdPgJU6dTkOYBrx0a60vzA1fuJrCddJNB1TgmDI=; b=KSvf21ARZexxG3kMuYJuR6uNVPYPbHkF4IRbEI3US0v+8WlLKBr69UXIPaawSkekclMDf+0rAU62pumuNf1ZD6hImhPqczABBaw3mdRkNcIOahFAKfK11SBfjbZ6nME+ToYZGVC4gYrNqrfvfDarOCgxtim0s44oyrvBM1DyVpU=;
In-Reply-To: <f7cb9c63-1eeb-89c0-2bb7-439794075279@case.edu>
User-Agent: Evolution 3.30.5-1.1
Authentication-Results: smtp39.i.mail.ru; auth=pass smtp.auth=rootlexx@mail.ru smtp.mailfrom=rootlexx@mail.ru
X-77F55803: 260C666A7D66B36A5A78504BD2AC29419866B4965ABE1B7A35924AEDF9EC6D8B4816D550AB0FFBDF5C3EDEED229BADBA
X-7FA49CB5: 0D63561A33F958A52C120B3F64D700FA87F31A7A6DC2D6218286FD09DEB44F198941B15DA834481FA18204E546F3947C062BEEFFB5F8EA3EF6B57BC7E64490618DEB871D839B7333395957E7521B51C2545D4CF71C94A83E9FA2833FD35BB23D27C277FBC8AE2E8B8C7ADC89C2F0B2A5A471835C12D1D977C4224003CC8364767815B9869FA544D8D32BA5DBAC0009BE9E8FC8737B5C2249A64C4E77951A82EE76E601842F6C81A12EF20D2F80756B5F5C318D1F9ECD513A76E601842F6C81A127C277FBC8AE2E8BFCB6192C5142207C3AA81AA40904B5D99449624AB7ADAF37F910319684D6E05D725E5C173C3A84C3EBF4D8D28E8B69030146B58C9A2D570C2B32DCB92A8600C6C4224003CC836476C0CAF46E325F83A50BF2EBBBDD9D6B0F93F060FBA3C93C613B503F486389A921A5CC5B56E945C8DA
X-Mailru-Sender: FD65D7C492470CAED3DD1703795F7E02278B5C5D865A13D4E69F76E426E9A78C53F209797D94BD8A15D893B5EE9B869EC77752E0C033A69ED2A0601D20520849A97B7613133B5FEC3453F38A29522196
X-Mras: OK
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized.
X-Received-From: 94.100.177.99
X-BeenThere: bug-bash@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-bash>
List-Post: <mailto:bug-bash@gnu.org>
List-Help: <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID: <f2e0255652f53d22135229ed61f27cca00a312fe.camel@mail.ru>
X-Mailman-Original-References: <3dd641953467a3299265e479026fc40a7bb697d4.camel@mail.ru> <68c76159-3cf3-b12f-9145-f0578d5415a3@case.edu> <db11c81c9312dec35fa6579db44dc03d03bb27fd.camel@mail.ru> <f7cb9c63-1eeb-89c0-2bb7-439794075279@case.edu>
Xref: csiph.com gnu.bash.bug:15664

В Ср, 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?