From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 24103@debbugs.gnu.org
Subject: bug#24103: 25.1.50; Add white space separator when appending string
Date: Fri, 29 Jul 2016 13:16:03 +0300 [thread overview]
Message-ID: <83h9b8rbq4.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1607291855190.6157@calancha-pc> (message from Tino Calancha on Fri, 29 Jul 2016 18:57:41 +0900 (JST))
> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Fri, 29 Jul 2016 18:57:41 +0900 (JST)
>
>
> I)
> emacs -Q ~
> M-: (goto-char (dired-subdir-min)) RET
> M-: (dired-goto-next-file) RET
> w
> ;; copied first file name into kill-ring
> M-: (dired-next-line 1) RET
> C-M-w w
> ;; This append second file name to the kill-ring.
> ;; Note that there is no separator between the first/second file name.
>
> II)
> emacs -Q ~
> M-: (goto-char (dired-subdir-min)) RET
> w
> ;; dir name copied into kill-ring
> M-: (goto-char (dired-subdir-max)) RET
> w
> ;; copied '' into kill-ring
>
> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> >From 80e9eb3fc790148a70dbf1da5d12e22681180bee Mon Sep 17 00:00:00 2001
> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Fri, 29 Jul 2016 18:53:38 +0900
> Subject: [PATCH] Add white space separator when appending string
>
> * lisp/dired.el (dired-copy-filename-as-kill):
> Add white space before string when command is appending.
> Copy just non-empty strings (Bug#24103).
Isn't this second-guessing what the user means? What if the kill ring
has "/foo/bar/" and the user wants to append a file name to that, thus
creating a valid absolute file name?
Thanks.
next prev parent reply other threads:[~2016-07-29 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 9:57 bug#24103: 25.1.50; Add white space separator when appending string Tino Calancha
2016-07-29 10:16 ` Eli Zaretskii [this message]
2016-07-29 10:27 ` Tino Calancha
2016-07-29 13:25 ` Eli Zaretskii
2016-07-29 14:29 ` Tino Calancha
2016-07-29 14:59 ` Eli Zaretskii
2016-07-30 8:29 ` bug#24103: (no subject) Tino Calancha
2016-07-30 8:48 ` Eli Zaretskii
2016-07-31 8:36 ` Tino Calancha
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=83h9b8rbq4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24103@debbugs.gnu.org \
--cc=tino.calancha@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).