From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48657@debbugs.gnu.org, moralesrodrigo1100@gmail.com
Subject: bug#48657: Defvar delimiter for dired-copy-filename-as-kill
Date: Sun, 24 Oct 2021 05:27:51 -0700 [thread overview]
Message-ID: <CADwFkmmk2vF+AVWezoXxUpWt4g4nJXH9e_2VvnndECVW08mULQ@mail.gmail.com> (raw)
In-Reply-To: <83bl3e4onq.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> I don't see why. A number of GNU programs use the null byte as a
> reliable delimiter in similar situations (Grep, xargs, etc.), so why
> shouldn't we do the same?
They usually only do so with a special command line argument (e.g. xargs).
> Why using a space when we know it will sometimes fail? The null byte
> will never fail, and Emacs is perfectly capable of handling strings
> with embedded null bytes.
This is a user facing command, so I think users might run into some
issues with it. For example, it might just be perceived as ugly.
In the "normal" case, when you deal with file names without spaces in
them, it also just seems more natural to use spaces.
Perhaps we could just detect if any of filenames have spaces in them
and use null byte delimiters if they do?
next prev parent reply other threads:[~2021-10-24 12:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 19:12 bug#48657: Defvar delimiter for dired-copy-filename-as-kill Rodrigo Morales
2021-05-25 19:34 ` Eli Zaretskii
2021-10-24 7:11 ` Stefan Kangas
2021-10-24 12:01 ` Eli Zaretskii
2021-10-24 12:27 ` Stefan Kangas [this message]
2021-10-24 14:01 ` Eli Zaretskii
2021-10-24 14:27 ` Stefan Kangas
2022-07-15 10:37 ` Lars Ingebrigtsen
2022-07-15 14:16 ` Drew Adams
2021-05-25 19:44 ` bug#48657: [External] : " Drew Adams
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=CADwFkmmk2vF+AVWezoXxUpWt4g4nJXH9e_2VvnndECVW08mULQ@mail.gmail.com \
--to=stefan@marxist.se \
--cc=48657@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=moralesrodrigo1100@gmail.com \
/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).