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.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,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 46e70c44 for ; Fri, 29 Nov 2019 20:37:58 +0000 (UTC) Received: (qmail 28365 invoked by alias); 29 Nov 2019 20:37:52 -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: 44957 Received: (qmail 27593 invoked by uid 1010); 29 Nov 2019 20:37:52 -0000 X-Qmail-Scanner-Diagnostics: from mx1.cock.li by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.0/25642. spamassassin: 3.4.2. Clear:RC:0(185.10.68.5):SA:0(-1.9/5.0):. Processed in 2.170298 secs); 29 Nov 2019 20:37:52 -0000 X-Envelope-From: zsugabubus@national.shitposting.agency X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at national.shitposting.agency designates 185.10.68.5 as permitted sender) Date: Fri, 29 Nov 2019 21:37:07 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=national.shitposting.agency; s=mail; t=1575059833; bh=J2KHIdmPs2X0MXwd5odQdqj/4QEE7wqJi03yJgLIyg4=; h=Date:From:To:Subject:References:In-Reply-To:From; b=bhUPhXvctR1tdCVKWYkvtwQLc6QEQemyWi+HXeoXzpmGxiY4sFBe3e5II9g4fVJGG xzv+R8z6BZJsPMSfyuGLAvFbon6Eo0CK1yD/yJzzX8pk7MIO2zcAVTxidjor9oVuXE Lot5FrtJ/xQEaiG33hmspvZobWF9vhN9N/8rGSZvYPVcTpI/ft3MZ23msrKZsaNWkm xhhArqcLsq3p9PDBuCWuPpZwvkB8IRlkH+eszpqxa0waMTBIrDsVAziweupu04E6gB 4meLB4ELfOJBr6HLPh/AGGOdNJ13RHMWQT0L3KO6YOfTuyFKNwabUPfUXfzV2XOXYY ucG3OR7oPHefQ== From: zsugabubus To: zsh-workers@zsh.org Subject: Re: Funky list-colors Message-ID: <20191129203707.ipf4zjkkptg35lpa@localhost> References: <20191129122141.rekf7hcxtacjojo2@localhost> <20191129172303.sd5bj3gukhdb7mpp@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Fri, Nov 29, 2019 at 11:22:52AM -0800, Bart Schaefer wrote: > On Fri, Nov 29, 2019 at 9:23 AM zsugabubus > wrote: > > > > Though the name clearly states that these are “colors”, but why this > > artificial limitation? Width measuring happens at the prompts too > > Prompts have the reverse assumption, that everything is nonzero width > (needs counting) unless special syntax indicates otherwise. The > overhead of designating the width of every color element and checking > whether it is greater than zero doesn't seem worth it, given that > we're sharing color definitions with other standard apps like "ls" and > none of THOSE support nonzero-width colors. > > > I really would like it to work > > Chances are there's a different way to do what you are trying to do. > What's the end goal here? Recently I completely get rid of terminal file managers because I realized that they are much-much less powerful than the "plain" shell could be. I can easily write small functions that do exactly what and how I need. To keep my message short, I wanted to receive a quick visual feedback what kind of files I work with. That's where `LS_COLORS` came into the view. However, if I'm only using 3-4 colors it looks like a rainbow (more colors can be hardly distinguished and remembered). I even had no luck with fuzzy finders, because: - fzf: I can't see the search highlights because of this rainbow (everything customize just the one I'd need not... hehh); - fzy: Doesn't customizable too much; - skim (fzf in rust): Can set background for search highlights (hurray) but fails to correctly display other colors. So after my success story with colors, I started modifying `LS_COLORS` to put prefixes before files. It's a way better solution from every point of view. Programs handle it as much as I need[1], but zsh's completion fails. .<- Here I'm now. Personally, I don't care about that few additional microseconds that zsh takes to parse that hundred 10 chars long string to compute how much space will it take up on the screen. Maybe, hiding it behind an shell option? 1: Expect `ls` grid view, but I can live without it.