From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsugabubus <zsugabubus@national.shitposting.agency>,
"zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Funky list-colors
Date: Thu, 5 Dec 2019 12:07:49 +0100 [thread overview]
Message-ID: <CAKc7PVDzpYUhR7TdoitmiHqvWVH20qGtruA6MhAsYqf2-8Kr5A@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7Y_TDFMU_uEHtEbmAUiNRLs2Ek_NdbhUU9fAzc8ZxAYww@mail.gmail.com>
On Thu, 5 Dec 2019 at 00:28, Bart Schaefer <schaefer@brasslantern.com> wrote:
> 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…
--
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
Blog: http://zdharma.org
next prev parent reply other threads:[~2019-12-05 11:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 12:21 zsugabubus
2019-11-29 16:06 ` Bart Schaefer
2019-11-29 17:23 ` zsugabubus
2019-11-29 19:22 ` Bart Schaefer
2019-11-29 20:37 ` zsugabubus
2019-12-04 23:27 ` Bart Schaefer
2019-12-05 7:44 ` Oliver Kiddle
2019-12-05 11:07 ` Sebastian Gniazdowski [this message]
2019-12-05 11:19 ` Roman Perepelitsa
2019-12-05 17:40 ` Oliver Kiddle
2019-12-07 20:58 ` zsugabubus
2019-12-07 21:42 ` Oliver Kiddle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKc7PVDzpYUhR7TdoitmiHqvWVH20qGtruA6MhAsYqf2-8Kr5A@mail.gmail.com \
--to=sgniazdowski@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
--cc=zsugabubus@national.shitposting.agency \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).