Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail From: Chet Ramey Newsgroups: gnu.bash.bug Subject: Re: [readline] Multibyte invisible chars cause weird prompt length calculation issue Date: Wed, 27 Nov 2019 11:48:32 -0500 Lines: 39 Approved: bug-bash@gnu.org Message-ID: References: <3dd641953467a3299265e479026fc40a7bb697d4.camel@mail.ru> <68c76159-3cf3-b12f-9145-f0578d5415a3@case.edu> Reply-To: chet.ramey@case.edu NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: usenet.stanford.edu 1574873330 5727 209.51.188.17 (27 Nov 2019 16:48:50 GMT) X-Complaints-To: action@cs.stanford.edu Cc: chet.ramey@case.edu To: =?UTF-8?B?0JDQu9C10LrRgdC10Lkg0KjQuNC70LjQvQ==?= , bug-bash@gnu.org Envelope-to: bug-bash@gnu.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=case.edu; s=smtp-primary; t=1574873311; bh=jr9JsQhp9fLMIKf3oO8fQLXAAg6TohQHS+Sd9+K3DGU=; h=Reply-To:Cc:Subject:To:References:From:Message-ID:Date: MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=cp8bBkZz0lftomNyDfH2ARuY7mwcENvlr3Zkqg7fPoSnAs1B3rp5glOZ616ZvgoP0H NrMwHHgIEEaBmyZ52t1OjHFH5GAmYAAVsDu3NmHnPG2BaB/KOk8fEh7nnB7X4EFCzzU yKDKp9PN7zF5htc3ob1zyK65PMcrJLzw1aFpUBR2s4xSp6Xfy7+szgV5u5Ehzj9yXjH EEc2Zc7DZ2UfRzgfMV7XcirLZ+RJ1+GwTCRyhGKfobTjf2gRbBa9mEZUurPwl7FVVVO XLZE1whCdC7k0V9ZGDNAnt8Bw14ZKP+c5SE/Hg0Q5Xr90CrXJxqsIs7HSoTNJHdFhK6 qYll0QZw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=case.edu; s=smtp-primary; t=1574873308; bh=nuBPmOJveVtWXRMYBFVGFgJdD1cjObWY+kpBRilNNYI=; h=Reply-To:Cc:Subject:To:References:From:Message-ID:Date: MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=m7qQPtGKPivWIV9FBUjN9YBI73hc2xU0GnM97fOaFeZIo+Evlf6sON8/VAC6HBGzNo AzcfPZD/MAktkY/8LKNc0c1vBYGJDL3U4+dm7e2abdEGRZ4Yq+IHWHJDGSYjaLnNegk e1We5oiZkvuilhyteq+FpqXjZA1uI77Q9q0IVUvCYvmi2XjGOPLnPQPPxMz2YGkKZEc AY82ZNWj0R3CRwIGhZQhfdOqRvdupjQM4U3g9UrcIgBD7DGD3NjsQe+weXKQN51w06H LeiDZ3pD3c7rin+kXk09GPOZ2s5ZeOJU1/MRn2CMLabi5Y1x8SrQcSwrJsX9yGxEkgB /M/BufoA== User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 In-Reply-To: Content-Language: en-US X-Junkmail-Status: score=7/90, host=mpv1-2015.case.edu X-Junkmail-PrAS-Raw: score=7/90, refid=2.7.2:2019.11.27.153617:17:7.944, ip=, rules=DKIM_SIGNATURE, __HAS_REPLYTO, __HAS_CC_HDR, __SUBJ_REPLY, __PHISH_SPEAR_SUBJ_ALERT, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __TO_MALFORMED_2, __TO_NAME, __TO_NAME_DIFF_FROM_ACC, __HAS_REFERENCES, __REFERENCES, __HAS_FROM, FROM_EDU_TLD, __HAS_MSGID, __SANE_MSGID, DATE_TZ_NA, __USER_AGENT, __MOZILLA_USER_AGENT, __MIME_VERSION, __IN_REP_TO, __CT, __CT_TEXT_PLAIN, __CTE, __REPLYTO_SAMEAS_FROM_ADDY, __REPLYTO_SAMEAS_FROM_ACC, __FROM_DOMAIN_IN_ANY_CC1, __FROM_DOMAIN_IN_ANY_CC2, __REPLYTO_SAMEAS_FROM_DOMAIN, __DKIM_ALIGNS_1, __DKIM_ALIGNS_2, __ANY_URI, __URI_MAILTO, __URI_WITH_PATH, __URI_NO_WWW, __HIGHBITS, __CP_URI_IN_BODY, __FRAUD_MONEY_BIG_COIN_DIG, __FRAUD_MONEY_CURRENCY_DOLLAR, __SUBJ_ALPHA_NEGATE, __URI_IN_BODY, __URI_NOT_IMG, __FORWARDED_MSG, __BODY_NO_MAILTO, __NO_HTML_TAG_RAW, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_1200_1299, [TRUNCATED], so=2010-03-03 19:42:08, dmn=2016-08-03-0138 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] [fuzzy] X-Received-From: 129.22.103.226 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: X-Mailman-Original-References: <3dd641953467a3299265e479026fc40a7bb697d4.camel@mail.ru> <68c76159-3cf3-b12f-9145-f0578d5415a3@case.edu> Xref: csiph.com gnu.bash.bug:15662 On 11/27/19 11:24 AM, Алексей Шилин wrote: > В Ср, 27/11/2019 в 11:02 -0500, Chet Ramey пишет: >> On 11/25/19 10:05 AM, Алексей Шилин wrote: >> >>> Bash Version: 5.0 >>> Patch Level: 11 >>> Release Status: release >>> >>> Description: >>> >>> I'm using the following PS1 prompt (Debian's default for normal >>> users): >>> >>> \[\e]0;\u@\h: >>> \w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[ >>> 00m\ >>> ]:\[\033[01;34m\]\w\[\033[00m\]\$ >>> >>> ...where the first block '\[\e]0;\u@\h: \w\a\]' is for setting >>> xterm's >>> title, and the rest is Debian's "fancy" shell prompt. >> >> Is there a literal newline in the prompt string? And is it in the >> middle >> of the non-printing character block? >> > > No, of course not. It's Evolution doing its thing, splitting the line. > Sorry for the confusion. OK. 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. -- ``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/