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 64f57d9c for ; Thu, 5 Dec 2019 11:08:43 +0000 (UTC) Received: (qmail 23833 invoked by alias); 5 Dec 2019 11:08:35 -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: 44984 Received: (qmail 21920 invoked by uid 1010); 5 Dec 2019 11:08:35 -0000 X-Qmail-Scanner-Diagnostics: from mail-vk1-f169.google.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(209.85.221.169):SA:0(-2.0/5.0):. Processed in 1.885285 secs); 05 Dec 2019 11:08:35 -0000 X-Envelope-From: sgniazdowski@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.221.169 as permitted sender) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=4l5CXtdqx2mXTcVRdmjqxo2rkwAa5ZkesLBDSbSdfL0=; b=digfIU5AIrH6ywzOEqdQPTmiYB3oaDKoekr9lXX/xUzL3qUW8dxcBbHIXEj3ayzCAQ zNJmDIGHFqx/h6U1PZyTyQiRnNywdA0E092hkQohpti6m0LKJ4UGuucxGZi69gYRYFMg t9LO8CPAccMsSsclyH2C6tpVLl45dVoQBiKe1nN4WLTytvodr0MiMTzWr/efOd9oE1kj H/YJSqBmdk88E0WxS32/mlky/cSbvdLlxKLbSJ+pPcADmjCc33pzP03euxXlsWaZYfrc UXrWs4zd0qumIuZNq3tILjFKnUaxoAgwSOpTn5rSIKyR9IXm9/OGN3rvua9BRx19ZXnc pxPA== X-Gm-Message-State: APjAAAVZ2uGmAnrIIu7uLWanDpPV1XkYJ6VeMD33fGlVt31bMqZeZepS +cf7oSIY4En1Dx9awiYVOVL6UGknhpxB5Y8tqQCvuABe X-Google-Smtp-Source: APXvYqxT1wN57flZt78NPkNuYW8kUAWlAnrzD0vu43Hlr1gLxAYcbpRJX7SGwtRPp8zQuKDFo0ZMeckJ2L9sHynstLo= X-Received: by 2002:a1f:cec2:: with SMTP id e185mr376515vkg.22.1575544079149; Thu, 05 Dec 2019 03:07:59 -0800 (PST) MIME-Version: 1.0 References: <20191129122141.rekf7hcxtacjojo2@localhost> <20191129172303.sd5bj3gukhdb7mpp@localhost> <20191129203707.ipf4zjkkptg35lpa@localhost> In-Reply-To: From: Sebastian Gniazdowski Date: Thu, 5 Dec 2019 12:07:49 +0100 Message-ID: Subject: Re: Funky list-colors To: Bart Schaefer Cc: zsugabubus , "zsh-workers@zsh.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, 5 Dec 2019 at 00:28, Bart Schaefer wrot= e: > OK, so what you want here is not to fiddle with the way completion > applies colors to the grid, but the way it populates the grid with > file names. > > The first and most straightforward thing you might do is set the > LIST_TYPES option (it should be set by default, but maybe it's become > turned off). This puts an identifiying character at the end of the > file name, e.g., character devices get a "%", block devices get a > "#", directories a "/", symlinks an "@", etc. (Oddly I can't find a > complete description of the identifying characters in the manual.) If > you have this set and are not seeing these marks, it may be because > your completion function is not using "compadd -f" to tell the > internals to treat the names as files. 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=E2=80=A6 --=20 Sebastian Gniazdowski News: https://twitter.com/ZdharmaI IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin Blog: http://zdharma.org