GNU bug report logs - #57350
29.0.50; dired and filenames containing newlines

Previous Next

Full log

Message #33 received at 57350 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: rms <at> gnu.org
Cc: larsi <at> gnus.org, 57350 <at> debbugs.gnu.org, robert <at> capuchin.co.uk
Subject: Re: bug#57350: 29.0.50; dired and filenames containing newlines
Date: Fri, 26 Aug 2022 09:54:20 +0300

> Cc: robert <at> capuchin.co.uk, 57350 <at> debbugs.gnu.org
> From: Richard Stallman <rms <at> gnu.org>
> Date: Thu, 25 Aug 2022 23:37:00 -0400
> 
> I had forgotten about the --dired option.  Now that someone has
> reminded us about it, what stands between us and using that option
> as the normal way?

A lot of coding.  The --dired option tells Emacs where the file name
begins and ends, but it does nothing to remove the literal newline
character in the Dired buffer that breaks the file name entry into two
(or more) lines.  So all the Dired commands that move by lines and
assume a file's entry takes only one line on display become broken and
have to be rewritten almost from scratch.

Patches are welcome to fix all of that.  There's no argument that
using -b is a band-aid, not a solution.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.