From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Po Lu <luangruo@yahoo.com>,
"sds@gnu.org" <sds@gnu.org>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: master 83e0442139f: There are no file modes on windows and dos
Date: Fri, 29 Sep 2023 15:53:29 +0000 [thread overview]
Message-ID: <SJ0PR10MB54882696ED4CABD6122BD3F7F3C0A@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83msx5ysr5.fsf@gnu.org>
> > * lisp/ls-lisp.el (ls-lisp-verbosity): Add `modes' on GNU and
> > Unix systems.
> > (ls-lisp-format): When `modes' is not in `ls-lisp-verbosity',
> > retain only the first character of `drwxrwxrwx'.
>
> I have much more serious issues with this change: it is an
> incompatible change in a long-standing behavior, which AFAIR was never
> discussed. Worse, it loses information: files that are read-only
> (something that _is_ supported on Windows) are no longer marked as
> unwritable, and executable files (not marked as such in the
> filesystem, but still a clearly existing attribute that we support) is
> not shown as such, either.
>
> I think if anything, this should (a) show 3-4 letters instead of just
> d or dash, i.e. drwx for a writable directory, -r-- for read-only
> files, -rwx for writable and executable files, etc; and (b) be an
> opt-in behavior, i.e. we need a new defcustom for it. In its current
> form, this change is not acceptable, sorry (and neither is the way of
> installing it without any discussion).
+1.
Please don't mess with the longstanding Dired behavior
showing file permissions. That will screw up habits
and font-locking.
For the most part, `ls-lisp' tries to match what `ls'
produces on, say, GNU/Linux - a feature, not a bug.
If someone wants to provide a minor mode that does
something different, that's a different story. But
the default, longstanding behavior of `ls-lisp' in
this regard should be kept/respected.
next prev parent reply other threads:[~2023-09-29 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <169586843825.5191.11036492923664810557@vcs2.savannah.gnu.org>
[not found] ` <20230928023358.9538BC06316@vcs2.savannah.gnu.org>
2023-09-28 3:21 ` master 83e0442139f: There are no file modes on windows and dos Po Lu
2023-09-29 14:10 ` Eli Zaretskii
2023-09-29 15:53 ` Drew Adams [this message]
2023-09-29 16:25 ` [External] : " Eli Zaretskii
2023-10-05 7:19 ` Eli Zaretskii
2023-10-06 16:55 ` Sam Steingold
2023-10-06 17:14 ` Corwin Brust
2023-10-07 5:38 ` Eli Zaretskii
2023-10-02 7:19 ` Michael Albinus
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=SJ0PR10MB54882696ED4CABD6122BD3F7F3C0A@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=sds@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).