From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 41ec3118 for ; Thu, 5 Dec 2019 17:41:43 +0000 (UTC) Received: (qmail 12624 invoked by alias); 5 Dec 2019 17:41:37 -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: List-Unsubscribe: X-Seq: 44986 Received: (qmail 12127 invoked by uid 1010); 5 Dec 2019 17:41:37 -0000 X-Qmail-Scanner-Diagnostics: from sonic313-21.consmr.mail.ir2.yahoo.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.1/25653. spamassassin: 3.4.2. Clear:RC:0(77.238.179.188):SA:0(-0.6/5.0):. Processed in 4.531368 secs); 05 Dec 2019 17:41:37 -0000 X-Envelope-From: okiddle@yahoo.co.uk X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _spf.mail.yahoo.com designates 77.238.179.188 as permitted sender) X-YMail-OSG: TRkZbS0VM1lq.mHdwc1if_ToDwjEb5AaW7zhXJ7tHxlEKRsLRQyikXf0N4ocLc3 TxckDpp7fb0MBMIUCXClgRJlAeDYAGFBa7R9BgnBpS4oqk8lqtC2R0GJeIne_4E9znp3fadwtLSM 7BFNtUI5q0vCsPqvDfHQ7C86VB.4oavL6FUqDD79xZIOik2kKFTTrj.OcZMWlQ6IuQ7d6OTAQLFs KUZjAJtelxohR_VU9Rbuj25cm1K06uEILQ1DcNY5Mp2Hq73pvdUKfJ4qDVVqDwkeKTTfRLnunHvU OIzOJZkPqOl28IUGu_EobTcR94ic0odWeXPKouimwzImix9lOuVvUdhyabsvWBHkjY93Gtvy4GXo lppkG6blAngLiCILdN2ETGF1BH31mI3Jcwq4frCXd5zNxPB.KD72ce7rvexYc.iQ.vaI2lp9LKY7 drdqa3eCs1O5dRZghGHqYgR2U2ZbnexyaQtLjSDyFVn1aRdA_0VuglaqSh5CFmFOhw0GRSOi58as 0awsRDl8hh4IBCuuRL1MaqKEHGw2LfYg79RrhiDowQp8.htJD1TDU9pTZNXF.DCXhFoMPCNv3NqQ QeClIYbiB5hT76p5EyHINlFEtcvXYBZJu_Lrb_n.vPjfH6Une2dPBolQfnPJodM4s1dVjlGv2ViW NmW.co6UCwLUvRQ6egRdhtEi8n5n3v8GU08R6WOCJ4fUOjUOYcizkUypCBJdKMBa__dJZZODh5eM vlUeec9pfS.nIXg9udIdWQ3TutpPssMMngHeyW.V3Bgm6V.HqImwHl5WDn0VlE4klFiialu9s6JK G9BD91umiG1H6S8DUJ9m_YJiAl3qd1z.ODL7vXdJWUFXPUk.GNsKqqBvw11o464wS0aYT2dwfdwW nvIXWFUXfB2jsdh1Mxv2GUqK9Ffef1Z6BAOH7AaFp1BOvMe8vqxbK3HqR7LTEG4Ukz2lPTEej.Hn Vg2B88EtGhq8U_1nklJ_uRwuom7MzCzBrHRAPjvhxgtGssdAg2wvVW9DQlPUbIiqvu_J0SNieSx0 YQBAiRFBj9zEIxAizyflU9nq68BhE6PyOgs07TCGqJOGVIt3txgwuxzQJ4jp9aepmtsjVjWMcYl8 Lv48sAepooF26ges362_CEkuvA6QR0EOcMSTSAGsVTTeSdLXqizOLTRvoKSEXdYyDys83nUNUoT7 3enQLxP2TPr3u6jBhe8CvPBc3Re59oqi0t0PvRMLJzxXHmVJP6yzfHl.tPbnHGREEEfoQIa3k3YV Jez4ukn6ErFVrqsQOROgKYKw83psz9LrksKYxeLUs1ymsIjTdWqhgfrmpX4mKEDI9WYgKqO_cYXv IUkviCcRxBgkvNLa5JAM3KK5gPZONMYafZY0rtU_M8bIdhslvtNeF.MhqM.1x5btcwwRj.gUs7lA 6DzAyeb2wrUkBdXLtb.QJoQ-- cc: "zsh-workers@zsh.org" In-reply-to: From: Oliver Kiddle References: <20191129122141.rekf7hcxtacjojo2@localhost> <20191129172303.sd5bj3gukhdb7mpp@localhost> <20191129203707.ipf4zjkkptg35lpa@localhost> To: Sebastian Gniazdowski Subject: Re: Funky list-colors MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <51239.1575567648.1@hydra> Content-Transfer-Encoding: 8bit Date: Thu, 05 Dec 2019 18:40:48 +0100 Message-ID: <51240-1575567648.316014@K4cq.pPN8.u6QO> X-Mailer: WebService/1.1.14728 hermes Apache-HttpAsyncClient/4.1.4 (Java/1.8.0_181) Sebastian Gniazdowski wrote: > This seems a less powerful than the hacky printable-LS_COLORS idea, > which I overall like. From experience, such things often result in > unpredictable and highly surprising + valuable solutions. Maybe it's > worth opening this door? In a most optimistic scenario, the code would > have to do a few isprints??? Such things also often result in weird bugs and broken feature combinations if they haven't been thought through properly. In this particular case, list-colors can take a form with just an equals sign (`=') followed by a pattern. The pattern is matched against the entire display string to specify colouring. But all the work related to ensuring column alignment has already been done at this stage. If you add extra visible characters, you may need to change the alignment but it is too late for that. As Bart mentioned there are already ways to define the exact form of completion display strings. So this wouldn't even add anything other than perhaps an easier configuration hook. If anyone has specific ideas for cases where extra decoration on matches would be useful, then patches to the relevant completion functions would be welcome. Oliver