From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Blaubogi <blaubogi@protonmail.com>, 31646-done@debbugs.gnu.org
Subject: bug#31646: 25.3; dired gets confused if filename contains linefeed char (\u000a) or (0x0a)
Date: Sat, 22 Aug 2020 21:35:02 -0400 [thread overview]
Message-ID: <CADwFkmmwEmX3cVYifGt3L2tDhjdjxjCwMtzrcgqQdhpiQa_Ggw@mail.gmail.com> (raw)
In-Reply-To: <83muwiuyvc.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 29 May 2018 20:59:19 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Tue, 29 May 2018 13:11:30 -0400
>> From: Blaubogi <blaubogi@protonmail.com>
>>
>> If a filename contains a linefeed character, dired does not escape it. Instead dired shows it in the buffer which
>> make the remaining characters of the name appear on the beginning of the next line. (using linefeed with code
>> 0x0A or unicode \u000a)
>>
>> -rwxrwxrwx 1 root 4 29.05.2018 12:37:14 ffff
>> -rwxrwxrwx 1 root 4 29.05.2018 18:42:22 test
>> test
>> -rwxrwxrwx 1 root 4 29.05.2018 12:37:14 vtvt
>>
>> This causes all kinds of trouble:
>> - file can't be deleted
>> - regular expression for file recognition doesn't work any longer:
>> 'no file on this line'
>> - hide-details mode does not show ANY files in this dir
>> - probably more
>
> Did you try adding -b to dired-listing-switches?
More information was requested, but none was given within over 2 years,
so I'm closing this bug. If this is still an issue, please reply to
this email (use "Reply to all" in your email client) and we can reopen
the bug report.
Best regards,
Stefan Kangas
prev parent reply other threads:[~2020-08-23 1:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 17:11 bug#31646: 25.3; dired gets confused if filename contains linefeed char (\u000a) or (0x0a) Blaubogi
2018-05-29 17:59 ` Eli Zaretskii
2020-08-23 1:35 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmmwEmX3cVYifGt3L2tDhjdjxjCwMtzrcgqQdhpiQa_Ggw@mail.gmail.com \
--to=stefan@marxist.se \
--cc=31646-done@debbugs.gnu.org \
--cc=blaubogi@protonmail.com \
--cc=eliz@gnu.org \
/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.