From: Andreas Schwab <schwab@suse.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: robert@capuchin.co.uk, larsi@gnus.org, 57350@debbugs.gnu.org,
rms@gnu.org
Subject: bug#57350: 29.0.50; dired and filenames containing newlines
Date: Wed, 24 Aug 2022 14:22:42 +0200 [thread overview]
Message-ID: <mvm4jy1esq5.fsf@suse.de> (raw)
In-Reply-To: <83bks97vs9.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 24 Aug 2022 13:58:30 +0300")
On Aug 24 2022, Eli Zaretskii wrote:
>> Cc: robert@capuchin.co.uk, 57350@debbugs.gnu.org
>> From: Richard Stallman <rms@gnu.org>
>> Date: Tue, 23 Aug 2022 23:53:58 -0400
>>
>> > If you have files with names with embedded newline characters, adding
>> > `b' to the switches will allow Dired to handle those files better.
>> > ---
>>
>> > But that has other side effects some people don't like, which is why we
>> > haven't changed the defaults.
>>
>> What do people dislike about -b?
>
> It causes much more than the newline to show up in somewhat awkward
> formatting. Most of those other characters don't need to be
> escaped/quoted for Emacs to DTRT, but 'ls' doesn't have any
> finer-tuned feature.
With support for --dired, there is already everything needed to handle
newlines in file names.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
prev parent reply other threads:[~2022-08-24 12:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 7:52 bug#57350: 29.0.50; dired and filenames containing newlines Robert Marshall
2022-08-23 10:53 ` Lars Ingebrigtsen
2022-08-24 3:53 ` Richard Stallman
2022-08-24 6:38 ` Michael Albinus
2022-08-24 10:24 ` Lars Ingebrigtsen
2022-08-26 3:37 ` Richard Stallman
2022-08-26 6:54 ` Eli Zaretskii
2022-08-31 2:38 ` Richard Stallman
2022-08-31 10:59 ` Eli Zaretskii
2022-08-31 11:06 ` Andreas Schwab
2022-08-31 12:32 ` Gregory Heytings
2022-08-24 10:58 ` Eli Zaretskii
2022-08-24 12:22 ` Andreas Schwab [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=mvm4jy1esq5.fsf@suse.de \
--to=schwab@suse.de \
--cc=57350@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=rms@gnu.org \
--cc=robert@capuchin.co.uk \
/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).