From: Juri Linkov <juri@linkov.net>
To: "Trent W. Buck" <trentbuck@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 24547@debbugs.gnu.org
Subject: bug#24547: 24.4; dired should colour in sockets and pipes
Date: Wed, 31 Jul 2019 23:45:44 +0300 [thread overview]
Message-ID: <87ftmmrkzr.fsf@mail.linkov.net> (raw)
In-Reply-To: <20190728145350.GA29513@goll.lan> (Trent W. Buck's message of "Mon, 29 Jul 2019 00:53:56 +1000")
>> What are the remaining special file types possible in ls output?
>>
>> For example, in /run I see only "s" and "p" files. But in /dev there are
>> also "b" and "c". These "block" and "character" device files could be
>> highlighted using the same face with sockets and pipes.
>
> As I hinted earlier, GNU ls's --color output is governed by the dircolors program.
> "dircolors --print-database" gives a bunch of stuff. The part you asked about is:
>
> DIR 01;34 # directory
> LINK 01;36 # symbolic link. (If you set this to 'target' instead of a
> # numerical value, the color is as for the file pointed to.)
> MULTIHARDLINK 00 # regular file with more than one link
> FIFO 40;33 # pipe
> SOCK 01;35 # socket
> DOOR 01;35 # door
> BLK 40;33;01 # block device driver
> CHR 40;33;01 # character device driver
> ORPHAN 40;31;01 # symlink to nonexistent file, or non-stat'able file ...
> MISSING 00 # ... and the files they point to
Thanks for the detailed explanation. I wonder what would be a common word
for these special file types: pipe, socket, block and character device?
Currently the face name is 'dired-socket', but this doesn't seem right
since it's used not only for socket, but also for pipe, block and character
devices. Is 'dired-special' a better name? At least the manual
(info "(coreutils) What information is listed") named them "special file".
next prev parent reply other threads:[~2019-07-31 20:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 8:05 bug#24547: 24.4; dired should colour in sockets and pipes Trent W. Buck
2019-07-27 14:26 ` Lars Ingebrigtsen
2019-07-27 22:07 ` Juri Linkov
2019-07-28 10:01 ` Lars Ingebrigtsen
2019-07-28 14:53 ` Trent W. Buck
2019-07-31 20:45 ` Juri Linkov [this message]
2019-08-01 2:17 ` Trent W. Buck
2019-08-01 11:08 ` Lars Ingebrigtsen
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=87ftmmrkzr.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=24547@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=trentbuck@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.