From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Nikishkin <lockywolf@gmail.com>
Cc: 46705@debbugs.gnu.org
Subject: bug#46705: 27.1; Dired fails to move files with newlines inside their names.
Date: Mon, 22 Feb 2021 19:02:27 +0200 [thread overview]
Message-ID: <83zgzwujbw.fsf@gnu.org> (raw)
In-Reply-To: <CA+A2iZYbdJNe2Vq7mvmPs-JsREU=SHVvrnA6Rw7PfM2nB_S1gw@mail.gmail.com> (message from Vladimir Nikishkin on Tue, 23 Feb 2021 00:11:37 +0800)
> From: Vladimir Nikishkin <lockywolf@gmail.com>
> Date: Tue, 23 Feb 2021 00:11:37 +0800
> Cc: 46705@debbugs.gnu.org
>
> Shouldn't "seeing" characters be independent of working with files?
If you use -b, you will be able to do both.
> I don't mind seeing newlines as line breaks, that's what they are, after all. Thunar shows them as line
> breaks.
>
> But shouldn't moving files work regardless? I'm using the coreutils version of ls, a fairly standard one.
There's nothing wrong with 'ls', but when a file name includes certain
special characters, Dired cannot cope with them, unless they are
presented suitably escaped. It's a known issue for which we don't
have a better solution than use -b.
next prev parent reply other threads:[~2021-02-22 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 13:36 bug#46705: 27.1; Dired fails to move files with newlines inside their names Vladimir Nikishkin
2021-02-22 15:51 ` Eli Zaretskii
2021-02-22 16:11 ` Vladimir Nikishkin
2021-02-22 17:02 ` Eli Zaretskii [this message]
2021-02-22 16:21 ` Lars Ingebrigtsen
2021-02-22 17:03 ` Eli Zaretskii
2021-02-22 21:39 ` Lars Ingebrigtsen
2021-02-22 17:21 ` bug#46705: [External] : " Drew Adams
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=83zgzwujbw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46705@debbugs.gnu.org \
--cc=lockywolf@gmail.com \
/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).