all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: larsi@gnus.org, 57350@debbugs.gnu.org, robert@capuchin.co.uk
Subject: bug#57350: 29.0.50; dired and filenames containing newlines
Date: Wed, 24 Aug 2022 13:58:30 +0300	[thread overview]
Message-ID: <83bks97vs9.fsf@gnu.org> (raw)
In-Reply-To: <E1oQhSo-0007aN-Bo@fencepost.gnu.org> (message from Richard Stallman on Tue, 23 Aug 2022 23:53:58 -0400)

> 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.





  parent reply	other threads:[~2022-08-24 10:58 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 [this message]
2022-08-24 12:22       ` Andreas Schwab

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83bks97vs9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=57350@debbugs.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.