From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24542 invoked by alias); 20 Mar 2017 14:33:57 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 40870 Received: (qmail 15026 invoked from network); 20 Mar 2017 14:33:56 -0000 X-Qmail-Scanner-Diagnostics: from new1-smtp.messagingengine.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(66.111.4.221):SA:0(-0.4/5.0):. Processed in 2.230856 secs); 20 Mar 2017 14:33:56 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.4 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: psprint3@fastmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at spf.messagingengine.com designates 66.111.4.221 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=Q+vbHe/FCvHvNiw2TaxePqL7i1tXj3R1vt3N5grrSpw=; b=lw7Mu6I1 YJqhThfh7c6WYKY8ZDzYe6Y9iep+coga7QGs13b9yDtYfC/XBGVC8EAnOjbmLHYn T83HUJm4VY9Rfj2djQycxvGcHUr+A4IycFGo+OytaeknOQYiAZGN5J0h9AMEYgZ5 t9Dj9qxP27dpAKCwhch+Qynn+Ee0nS8dghnQ90hEdhfCXHTnpsXWKmitT3Usp6Us KH0YmFG8pDBUqT0akKRzptOcA3x0mdCwzoPSfNPC0bqoFcHPWWN042HiZavDPGOC 1/RVo/Wjv/goPqTHuPgwPlxpLyaJ5t87iDxvV3kyfvhjc9faALpPUN73RBjHCefG 3ew4zRTLdgkWdg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=Q+vbHe/FCvHvNiw2TaxePqL7i1tXj 3R1vt3N5grrSpw=; b=ESpnz4xioo9OH0y1RDnyCe6hTMNjUixGojXBOiD7WFw+l F2K+jVxGzmGiDvy9pBYWvi9LRdMMoVERDwsyKSeetNd1wQ8gADzzBa95erm3Pv8Y D7O6QlCedHCDvbnwTDNfuQC99s1Wh2qzENzPFynrTDEbbvdeyjVSLDqLiXQzzaYs f6MeeN9wX+3IKKztvzW3E8B+XX8kaxp/EPXxTC414Q5IgSFlc4mkrZCYiC8lIfPX awodZzBYOjs6A55TdWTsBQ3a2QBkw34D//VLCncqheINcwAb20yKv449xRBbDPnD dBesOb/bkgqU1XkYrWymgQ4tLDSOv9sJ973PdUnXQ== X-ME-Sender: Message-Id: <1490020425.2614066.917182456.0E56E387@webmail.messagingengine.com> From: Sebastian Gniazdowski To: zsh-workers@zsh.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-aac97429 Subject: (m)-flag for boundary cases Date: Mon, 20 Mar 2017 07:33:45 -0700 Hello, % a=3D"=E6=BC=A2=E5=AD=97" % echo ${(mr:3::_:)a} =E6=BC=A2=E5=AD=97 % echo ${(mr:2::_:)a} =E6=BC=A2 I think it would be better to trim first case down to single Asian character, and display: =E6=BC=A2_. The point is that it gives predictable width. Current version is occasionally 1 character too long. I wonder how many people use (m)-flag. Never seen it mentioned here. I think that nobody wants the off-by-1 behavior, and fixing it will not break things, but make them automatically better, like for me =E2=80=93 the= flag turned out to be a necessity and a solution, with acceptable off-by-1 problem, which will be automatically fixed by Zsh update. I've added Asian characters support to ZUI via the flag, most important use case is the (r) padding, but also good cooperation with (P) flag. --=20 Sebastian Gniazdowski psprint3@fastmail.com