bug#31646: 25.3; dired gets confused if filename contains linefeed char (\u000a) or (0x0a)

[Stefan Kangas]

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