unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Zhu Zihao" <all_but_last@163.com>
To: "Lars Ingebrigtsen" <larsi@gnus.org>
Cc: 43789@debbugs.gnu.org
Subject: bug#43789: Re: bug#43789: 27.1; Dired cannot handle file which name contains linebreak
Date: Mon, 5 Oct 2020 15:47:43 +0800 (CST)	[thread overview]
Message-ID: <956b63c.162e.174f7bb05d7.Coremail.all_but_last@163.com> (raw)
In-Reply-To: <87362tqfxx.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 450 bytes --]

It generally follows the escape rule of string in Elisp I think.





















At 2020-10-05 15:39:54, "Lars Ingebrigtsen" <larsi@gnus.org> wrote:
>Eli Zaretskii <eliz@gnu.org> writes:
>
>> I think this would have unwanted effect on other control characters.
>> ISTR this was discussed in the past, but I cannot find that discussion
>> at the moment.
>
>I experimented a bit with two files, one with a newline and one with a
>C-b character:
>

[-- Attachment #2: Type: text/html, Size: 892 bytes --]

  reply	other threads:[~2020-10-05  7:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-04  8:58 bug#43789: 27.1; Dired cannot handle file which name contains linebreak Zhu Zihao
2020-10-04  9:36 ` Eli Zaretskii
2020-10-04  9:49   ` bug#43789: " Zhu Zihao
2020-10-04 10:54     ` Eli Zaretskii
2020-10-05  7:39       ` Lars Ingebrigtsen
2020-10-05  7:47         ` Zhu Zihao [this message]
2020-10-05  7:49         ` Andreas Schwab
2020-10-05  8:10           ` Eli Zaretskii
2020-10-05  8:18             ` bug#43789: " Zhu Zihao
2020-10-05  9:40               ` Eli Zaretskii
2020-10-05  8:26             ` Lars Ingebrigtsen
2020-10-05  9:30 ` Michael Albinus
2020-10-05  9:51   ` Eli Zaretskii
2020-10-06 16:11     ` bug#43789: " Zhu Zihao
2020-10-06 16:25       ` Eli Zaretskii
2020-10-05 16:53   ` Drew Adams
2020-10-06  2:30   ` Richard Stallman
2020-10-06  8:59     ` Michael Albinus

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=956b63c.162e.174f7bb05d7.Coremail.all_but_last@163.com \
    --to=all_but_last@163.com \
    --cc=43789@debbugs.gnu.org \
    --cc=larsi@gnus.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 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).