From: "Zhu Zihao" <all_but_last@163.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
larsi@gnus.org, 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 16:18:11 +0800 (CST) [thread overview]
Message-ID: <2acd8d27.1818.174f7d6ea35.Coremail.all_but_last@163.com> (raw)
In-Reply-To: <831riddre4.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 470 bytes --]
If "\002" can be display like ^B, we can make "\n" display like ^J in dired.
At 2020-10-05 16:10:59, "Eli Zaretskii" <eliz@gnu.org> wrote:
>> From: Andreas Schwab <schwab@linux-m68k.org>
>> Cc: Eli Zaretskii <eliz@gnu.org>, 43789@debbugs.gnu.org, Zhu Zihao
>> <all_but_last@163.com>
>> Date: Mon, 05 Oct 2020 09:49:13 +0200
>>
>> One downside is that -b isn't POSIX.
>
>Right.
>
>I'm also not sure everyone would like to see \002 instead of ^B.
[-- Attachment #2: Type: text/html, Size: 936 bytes --]
next prev parent reply other threads:[~2020-10-05 8:18 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 ` bug#43789: " Zhu Zihao
2020-10-05 7:49 ` Andreas Schwab
2020-10-05 8:10 ` Eli Zaretskii
2020-10-05 8:18 ` Zhu Zihao [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2acd8d27.1818.174f7d6ea35.Coremail.all_but_last@163.com \
--to=all_but_last@163.com \
--cc=43789@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=schwab@linux-m68k.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.