From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Philip Kaludercic <philipk@posteo.net>, 58664@debbugs.gnu.org
Subject: bug#58664: 29.0.50; Dired fails to operate on files with newline charachters in name
Date: Thu, 24 Nov 2022 12:01:55 -0800 [thread overview]
Message-ID: <CADwFkm=FLz_cD8O7aB=RAu1g9jaH6bFdQP1ORY-MnKdZgEOQsA@mail.gmail.com> (raw)
In-Reply-To: <83tu3ywfc0.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 20 Oct 2022 20:54:39 +0300")
tags 58664 + wontfix
close 58664
thanks
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Philip Kaludercic <philipk@posteo.net>
>> Date: Thu, 20 Oct 2022 17:39:12 +0000
>>
>>
>> If I create a file in the shell using
>>
>> $ touch "one
>> two"
>> $ ls
>> 'one'$'\n''two'
>>
>> and try to open this directory using Dired, I get the following
>>
>> -rw-r--r--. 1 philip philip 0 Oct 20 19:37 one
>> two
>>
>> where the "t" in two is highlighted. If I try to mark the file and
>> delete it, Dired attempts to delete the file "one", that luckily doesn't
>> exist.
>
> This is a known issue. The best solution we have for it is to use -b
> in the ls switches used by Dired. (That cannot be the default because
> -b has adverse effect in other cases.)
So I think this is a wontfix. I'm therefore closing this bug report.
prev parent reply other threads:[~2022-11-24 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 17:39 bug#58664: 29.0.50; Dired fails to operate on files with newline charachters in name Philip Kaludercic
2022-10-20 17:51 ` Stephen Berman
2022-10-20 17:54 ` Eli Zaretskii
2022-11-24 20:01 ` Stefan Kangas [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='CADwFkm=FLz_cD8O7aB=RAu1g9jaH6bFdQP1ORY-MnKdZgEOQsA@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=58664@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=philipk@posteo.net \
/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).