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

[GNU bug Tracking System]

Your message dated Sat, 22 Aug 2020 21:35:02 -0400
with message-id 
<CADwFkmmwEmX3cVYifGt3L2tDhjdjxjCwMtzrcgqQdhpiQa_Ggw@mail.gmail.com>
and subject line Re: bug#31646: 25.3; dired gets confused if filename contains 
linefeed char (\u000a) or (0x0a)
has caused the debbugs.gnu.org bug report #31646,
regarding 25.3; dired gets confused if filename contains linefeed char (\u000a) 
or (0x0a)
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
31646: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=31646
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: 25.3; dired gets confused if filename contains linefeed char (\u000a) or (0x0a) Date: Tue, 29 May 2018 13:11:30 -0400

Hello,

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 ffff

  -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

System:

In GNU Emacs 25.3.1 (x86_64-suse-linux-gnu, GTK+ Version 3.20.10)

of 2018-05-25 built on lamb08

Windowing system distributor 'The X.Org Foundation', version 11.0.11803000

System Description: openSUSE Leap 42.3

ext4 filesystem.

To reproduce:

Using ruby I created a file like this:

dir = "/mnt/loop0/test"

fname = "test" + "\u000a" + "test"

File.open(File.join(dir, fname), "w") { |fd| fd.write("test") }

M-x dired /mnt/loop0/test

I didn't test emacs under Microsoft Windows.

I did test using ntfs filesystem instead of ext4 which makes no difference.

Best regards

Sent from ProtonMail, Swiss-based encrypted email.

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#31646: 25.3; dired gets confused if filename contains linefeed char (\u000a) or (0x0a)
>
>
>
>
> Date: 
>
> Sat, 22 Aug 2020 21:35:02 -0400
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)
>
>
>
>
> 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
>
>
> --- End Message ---