unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Richard Stallman <rms@gnu.org>
Cc: Lars Ingebrigtsen <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 08:38:16 +0200	[thread overview]
Message-ID: <87sflmf8o7.fsf@gmx.de> (raw)
In-Reply-To: <E1oQhSo-0007aN-Bo@fencepost.gnu.org> (Richard Stallman's message of "Tue, 23 Aug 2022 23:53:58 -0400")

Richard Stallman <rms@gnu.org> writes:

Hi Richard,

>   > But you can make it work by changing `dired-listing-switches':
>
>   > ---
>   > 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?

Tramp, for example, has banned newlines in file names:

--8<---------------cut here---------------start------------->8---
(defconst tramp-localname-regexp "[^\n\r]*\\'"
  "Regexp matching localnames.")
--8<---------------cut here---------------end--------------->8---

Best regards, Michael.





  reply	other threads:[~2022-08-24  6:38 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 [this message]
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

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=87sflmf8o7.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --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 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).