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 16:25:32 +0300 [thread overview]
Message-ID: <83eg6cr2yb.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1607291917020.6754@calancha-pc> (message from Tino Calancha on Fri, 29 Jul 2016 19:27:30 +0900 (JST))
> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Fri, 29 Jul 2016 19:27:30 +0900 (JST)
> cc: Tino Calancha <tino.calancha@gmail.com>, 24103@debbugs.gnu.org
>
> On Fri, 29 Jul 2016, Eli Zaretskii wrote:
> > 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?
> Maybe, but not so standard way; we can skip that part of the fix, though.
Sorry, I don't understand: which part of the fix you suggest to skip,
and what will be left then?
> The command provide a nice way to do that as mentioned in the doc string:
> C-u 0 w
No, that produces the absolute names of files in the directory shown
by Dired, whereas what I meant is constructing a name of a file in
another directory by concatenating a directory killed in another kill
command and the file name killed by 'w'.
next prev parent reply other threads:[~2016-07-29 13:25 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
2016-07-29 10:27 ` Tino Calancha
2016-07-29 13:25 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83eg6cr2yb.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 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.