unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuri D'Elia <wavexx@thregr.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63142@debbugs.gnu.org
Subject: bug#63142: 30.0.50; QUOTING_STYLE can break dired
Date: Fri, 28 Apr 2023 20:01:01 +0200	[thread overview]
Message-ID: <87fs8j28aw.fsf@wavexx.thregr.org> (raw)
In-Reply-To: <83v8hgqo7c.fsf@gnu.org>

On Fri, Apr 28 2023, Eli Zaretskii wrote:
>> > I'd suggest first to report this to Coreutils maintainers: it makes
>> > little sense to me to honor QUOTING_STYLE when --dired is specified.
>> > If the Coreutils folks decline to handle this, then I guess we will
>> > have to.
>>
>> What sort of output should ls use in --dired mode?
>
> The default one, I think.  --dired already produces the information
> which tells where each file name begins and ends, so any quoting
> sounds redundant, no?

So searching through coreutils I find this old report:

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23024

| On further analysis I see that --dired mode already distinguishes
| the quoting-style in its output.  Also we had already documented
| that --dired should specify a --quoting-style to get consistent output.

Which huh, does mention this in the ls manual:

| If you use a quoting style like ‘--quoting-style=c’ (‘-Q’) that
|  adds quote marks, then the offsets include the quote marks.  So
|  beware that the user may select the quoting style via the
|  environment variable ‘QUOTING_STYLE’.  Hence, applications using
|  ‘--dired’ should either specify an explicit
|  ‘--quoting-style=literal’ (‘-N’) option on the command line, or
|  else be prepared to parse the escaped names.

Then it references a commit mentioning an emacs fix:

https://github.com/emacs-mirror/emacs/commit/e4adb6

which however seems to apply to tramp only.





  reply	other threads:[~2023-04-28 18:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28  9:35 bug#63142: 30.0.50; QUOTING_STYLE can break dired Yuri D'Elia
2023-04-28 10:27 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-28 10:28 ` Eli Zaretskii
2023-04-28 10:37   ` Yuri D'Elia
2023-04-28 10:46     ` Eli Zaretskii
2023-04-28 18:01       ` Yuri D'Elia [this message]
2023-04-29 10:46         ` Eli Zaretskii
2023-04-29 15:05           ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-29 15:16             ` Eli Zaretskii
2023-05-02  9:35               ` Yuri D'Elia
2023-05-02 12:18                 ` Eli Zaretskii
2023-05-02 15:57                   ` Yuri D'Elia
2023-05-02 17:48                     ` Eli Zaretskii
2023-05-05 11:04 ` Mattias Engdegård
2023-05-05 11:06   ` Yuri D'Elia
2023-05-05 11:25   ` Eli Zaretskii
2023-05-05 12:03     ` Michael Albinus
2023-05-05 12:11       ` Mattias Engdegård
2023-05-05 14:44         ` Michael Albinus
2023-05-05 17:26           ` Mattias Engdegård
2023-05-05 13:28       ` Eli Zaretskii

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=87fs8j28aw.fsf@wavexx.thregr.org \
    --to=wavexx@thregr.org \
    --cc=63142@debbugs.gnu.org \
    --cc=eliz@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).