Re: master 83e0442139f: There are no file modes on windows and dos

[Corwin Brust <corwin@bru.st>]

On Fri, Oct 6, 2023 at 11:55 AM Sam Steingold <sds@gnu.org> wrote:
>
> > * Eli Zaretskii <ryvm@tah.bet> [2023-09-29 17:10:54 +0300]:
> >
> >> * 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 came back to windows after a decade-long hiatus and found this feature
> (ls-lisp-verbosity) and thought that lack of mode removing was a simple
> oversight.
>

>
> I did not realize that this notion of permission exists in the MS world
> - but, I suppose, it depends on the FS and NTFS probably supports some
> form of it.
>

Would you consider reverting this change and posting as patches?  I
would be happy to try them, if so; although, I may need guidance (how?
what's expected?).

Also, I would be grateful if you explain the problem you are solving
in terms of how I might run into it.