From: Drew Adams <drew.adams@oracle.com>
To: Michael Albinus <michael.albinus@gmx.de>,
Zhu Zihao <all_but_last@163.com>
Cc: 43789@debbugs.gnu.org
Subject: bug#43789: 27.1; Dired cannot handle file which name contains linebreak
Date: Mon, 5 Oct 2020 09:53:15 -0700 (PDT) [thread overview]
Message-ID: <7af2342b-0d97-4002-a859-99c1fe7aafcf@default> (raw)
In-Reply-To: <87tuv9uiid.fsf@gmx.de>
> > 1. Use touch from coreutils or find-file in Emacs to create a file
> > which name contains a linebreak. (e.g. "line\nbreak")
> > 2. Visit it in dired, you cannot do anything with this file because
> > the characters after "\n" was ignored by dired.
>
> I recommend to avoid file names containing line breaks. Tramp, for
> example, cannot handle them at all.
And it's likely to mess up font-locking and other
Dired features that expect a newline to indicate
the end of a Dired line.
Dired, and other line-oriented displays, are a bit
fragile in this respect.
next prev parent reply other threads:[~2020-10-05 16:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 8:58 bug#43789: 27.1; Dired cannot handle file which name contains linebreak Zhu Zihao
2020-10-04 9:36 ` Eli Zaretskii
2020-10-04 9:49 ` bug#43789: " Zhu Zihao
2020-10-04 10:54 ` Eli Zaretskii
2020-10-05 7:39 ` Lars Ingebrigtsen
2020-10-05 7:47 ` bug#43789: " Zhu Zihao
2020-10-05 7:49 ` Andreas Schwab
2020-10-05 8:10 ` Eli Zaretskii
2020-10-05 8:18 ` bug#43789: " Zhu Zihao
2020-10-05 9:40 ` Eli Zaretskii
2020-10-05 8:26 ` Lars Ingebrigtsen
2020-10-05 9:30 ` Michael Albinus
2020-10-05 9:51 ` Eli Zaretskii
2020-10-06 16:11 ` bug#43789: " Zhu Zihao
2020-10-06 16:25 ` Eli Zaretskii
2020-10-05 16:53 ` Drew Adams [this message]
2020-10-06 2:30 ` Richard Stallman
2020-10-06 8:59 ` Michael Albinus
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=7af2342b-0d97-4002-a859-99c1fe7aafcf@default \
--to=drew.adams@oracle.com \
--cc=43789@debbugs.gnu.org \
--cc=all_but_last@163.com \
--cc=michael.albinus@gmx.de \
/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).