From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: larsi@gnus.org, 57350@debbugs.gnu.org, robert@capuchin.co.uk
Subject: bug#57350: 29.0.50; dired and filenames containing newlines
Date: Fri, 26 Aug 2022 09:54:20 +0300 [thread overview]
Message-ID: <8335dj336r.fsf@gnu.org> (raw)
In-Reply-To: <E1oRQ9U-0008GK-Qo@fencepost.gnu.org> (message from Richard Stallman on Thu, 25 Aug 2022 23:37:00 -0400)
> Cc: robert@capuchin.co.uk, 57350@debbugs.gnu.org
> From: Richard Stallman <rms@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.
next prev parent reply other threads:[~2022-08-26 6:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 7:52 bug#57350: 29.0.50; dired and filenames containing newlines Robert Marshall
2022-08-23 10:53 ` Lars Ingebrigtsen
2022-08-24 3:53 ` Richard Stallman
2022-08-24 6:38 ` Michael Albinus
2022-08-24 10:24 ` Lars Ingebrigtsen
2022-08-26 3:37 ` Richard Stallman
2022-08-26 6:54 ` Eli Zaretskii [this message]
2022-08-31 2:38 ` Richard Stallman
2022-08-31 10:59 ` Eli Zaretskii
2022-08-31 11:06 ` Andreas Schwab
2022-08-31 12:32 ` Gregory Heytings
2022-08-24 10:58 ` Eli Zaretskii
2022-08-24 12:22 ` Andreas Schwab
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=8335dj336r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57350@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rms@gnu.org \
--cc=robert@capuchin.co.uk \
/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).