unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Gereon Kaiping <gereon.kaiping@gmail.com>
Cc: 24184@debbugs.gnu.org
Subject: bug#24184: 25.0.94; dired-copy-filename-as-kill does not quote or properly separate file names
Date: Mon, 16 Apr 2018 01:13:38 +0200	[thread overview]
Message-ID: <87a7u45ahp.fsf@mouse.gnus.org> (raw)
In-Reply-To: <CA+mEJ1sFNeFZsCpghB_wyhAnQpRs8gCdTp1w-h-VutHcDG4m6g@mail.gmail.com> (Gereon Kaiping's message of "Mon, 8 Aug 2016 16:08:40 +0200")

Gereon Kaiping <gereon.kaiping@gmail.com> writes:

> $ touch "this file" "that file"
> $ emacs -Q
> C-x C-f RET m m w
>
> gives
>
> that file this file
>
> but should give something like
>
> "that file" "this file"
>
> or
>
> that file
> this file
>
> to be much more useful. The former looks cleanest, because then the
> content can be yanked as elisp list, but would of course require that
> not only filenames are quoted, but that also " be quoted inside file
> names.

Hm...  I guess that depends on what the purpose of the copy-as-kill is.
In the single file case, we probably don't want to quote "this file"
because then we can't use that to yank it into the file prompt, for
instance.

But in the several-file case, we can't use it for that anyway, and then
quoting these file names is probably better than not.

Hm...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2018-04-15 23:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08 14:08 bug#24184: 25.0.94; dired-copy-filename-as-kill does not quote or properly separate file names Gereon Kaiping
2018-04-15 23:13 ` Lars Ingebrigtsen [this message]
2018-04-16 20:40   ` Juri Linkov
2018-04-16 22:35     ` Drew Adams
2021-08-15 12:24       ` Lars Ingebrigtsen

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=87a7u45ahp.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=24184@debbugs.gnu.org \
    --cc=gereon.kaiping@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).