From: Eli Zaretskii <eliz@gnu.org>
To: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: 23.0.60; on Mac OS X permissions of group-writable files are displayed with red w
Date: Mon, 26 May 2008 23:00:31 +0300 [thread overview]
Message-ID: <uk5hgg7j4.fsf@gnu.org> (raw)
In-Reply-To: <F77F812E-645E-4939-98B3-38E2F801F123@Web.DE>
> From: Peter Dyballa <Peter_Dyballa@Web.DE>
> Date: Mon, 26 May 2008 21:11:49 +0200
> Cc:
>
> GNU Emacs explains to me (after following hypertext links from *Help*
> buffers) that dired-perm-write face comes out of dired.el, from these
> lines:
>
> (defface dired-perm-write
> '((((type w32 pc)) :inherit default) ;; These default to rw-rw-rw.
> ;; Inherit from font-lock-comment-delimiter-face since with min-
> colors 8
> ;; font-lock-comment-face is not colored any more.
> (t (:inherit font-lock-comment-delimiter-face)))
> "Face used to highlight permissions of group- and world-writable
> files."
> :group 'dired-faces
> :version "22.2")
>
> I am pretty sure that I neither have some MS stuff on my lap nor a PC
> in use ... so why do I see these red w in drwxrwxr-x or -rw-rw-r-- ?
You see them precisely _because_ you never had any MS stuff on your
lap. Look at the defface above: it says that on w32 and MSDOS (that's
what `pc' means) dired-perm-write face is identical to the default
face, whereas on all other systems it looks like
font-lock-comment-delimiter-face.
This feature is meant to make world-writable files to stand out on
systems where it isn't the default, presumably to alert you to
possible security holes.
prev parent reply other threads:[~2008-05-26 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 19:11 23.0.60; on Mac OS X permissions of group-writable files are displayed with red w Peter Dyballa
2008-05-26 20:00 ` Eli Zaretskii [this message]
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=uk5hgg7j4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Peter_Dyballa@Web.DE \
--cc=emacs-pretest-bug@gnu.org \
/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).