unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "Trent W. Buck" <trentbuck@gmail.com>, 24547@debbugs.gnu.org
Subject: bug#24547: 24.4; dired should colour in sockets and pipes
Date: Sun, 28 Jul 2019 01:07:39 +0300	[thread overview]
Message-ID: <875znnxhas.fsf@mail.linkov.net> (raw)
In-Reply-To: <871rybh7u8.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Sat, 27 Jul 2019 16:26:23 +0200")

>> With GNU ls --color in a terminal, different colors are used for
>>
>>     regular files,
>>     directories,
>>     symlinks,
>>     sockets,
>>     pipes,
>>     (other stuff - dircolors?)
>>
>> In dired, the first three get different faces,
>> but sockets and pipes look like regular files.
>>
>> I think it's probably easy to fix sockets and pipes,
>> because the first character is "s" or "p",
>> at least in GNU ls output.
>
> Sounds reasonable.  I've now done this in Emacs 27, but I've used just a
> single face for both sockets and pipes.

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.





  reply	other threads:[~2019-07-27 22:07 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 [this message]
2019-07-28 10:01     ` Lars Ingebrigtsen
2019-07-28 14:53     ` Trent W. Buck
2019-07-31 20:45       ` Juri Linkov
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875znnxhas.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).