From: Paul R <paul.r.ml@gmail.com>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Opening file with is in killring
Date: Fri, 31 Oct 2008 15:40:20 +0100 [thread overview]
Message-ID: <87hc6s6d63.fsf@gmail.com> (raw)
In-Reply-To: <001001c93b65$6125c250$0200a8c0@us.oracle.com> (Drew Adams's message of "Fri, 31 Oct 2008 07:31:35 -0700")
Hello Drew,
Drew> Not sure what you're saying, but I think you're referring to
Drew> yanking an absolute file name, or a file name that starts with
Drew> `~', after the default directory name in the minibuffer. If so,
Drew> that is not new but has been an Emacs feature for decades. But it
Drew> only works if the file name you yank is absolute or starts with
Drew> `~'.
I haven't been using emacs for decades yet, so it was just in case.
Drew> If a relative file name (e.g. `foo.el') is in the kill ring, then
Drew> I know of nothing quicker than clearing the minibuffer and then
Drew> yanking.
But in such a case, it would try to expand the relative file name from
default-directory, which is precisely the one printed by default in the
prompt, isn't it ? In this case, why remove the default prompt ? Just
yanking after should yield to the same result with fewer keystrokes.
--
Paul
next prev parent reply other threads:[~2008-10-31 14:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 10:17 Opening file with is in killring Decebal
2008-10-31 12:28 ` Paul R
2008-10-31 14:31 ` Drew Adams
2008-10-31 14:40 ` Paul R [this message]
2008-10-31 15:16 ` Drew Adams
[not found] ` <mailman.2573.1225466182.25473.help-gnu-emacs@gnu.org>
2008-11-01 8:27 ` Decebal
[not found] ` <mailman.2570.1225463508.25473.help-gnu-emacs@gnu.org>
2008-11-01 8:24 ` Decebal
2008-11-01 8:29 ` Teemu Likonen
2008-11-01 20:07 ` Decebal
2008-11-01 16:45 ` Drew Adams
[not found] ` <mailman.2644.1225557931.25473.help-gnu-emacs@gnu.org>
2008-11-01 20:20 ` Decebal
[not found] ` <mailman.2561.1225456153.25473.help-gnu-emacs@gnu.org>
2008-10-31 14:39 ` Decebal
2008-11-01 13:41 ` Kevin Rodgers
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=87hc6s6d63.fsf@gmail.com \
--to=paul.r.ml@gmail.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.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.
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).