From: Kyle Meyer <kyle@kyleam.com>
To: "Sebastian Reuße" <seb@wirrsal.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH 2/2] org-refile: optionally prefix refile targets with buffer name
Date: Fri, 05 May 2017 19:23:25 -0400 [thread overview]
Message-ID: <87tw4ysxaq.fsf@kyleam.com> (raw)
In-Reply-To: <20170503203046.31610-2-seb@wirrsal.net>
Sebastian Reuße <seb@wirrsal.net> writes:
> * org.el (org-refile-get-targets): Add case to optionally prefix
> refile targets with the buffer name.
> (org-refile-use-outline-path): Add new option setting and document.
>
> Having an option to use the buffer name as a prefix is convenient,
> since this will work hand in hand with uniquify to only show those
> parts of the filesystem path needed to disambiguate buffers of
> identically named files, as opposed to prefixing refile targets with
> the full filesystem path.
Yeah, that does seem useful.
> ---
> lisp/org.el | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
I think this should be accompanied by an ORG-NEWS entry.
> diff --git a/lisp/org.el b/lisp/org.el
> index ad92f3b2e..342143d5a 100644
> --- a/lisp/org.el
> +++ b/lisp/org.el
> @@ -2553,13 +2553,16 @@ (defcustom org-refile-use-outline-path nil
> into the path. In this case, you can also stop the completion after
> the file name, to get entries inserted as top level in the file.
>
> -When `full-file-path', include the full file path."
> +When `full-file-path', include the full file path.
> +
> +When `id', use the buffer name."
The link between `id' and buffer name isn't obvious to me. I'm guessing
that it's because it would be a unique ID for the file, whereas `file'
would not. Perhaps `buffer' would be better?
--
Kyle
next prev parent reply other threads:[~2017-05-05 23:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 17:50 [PATCH 1/2] org-refile: escape slashes only in headline of refile target Sebastian Reuße
2017-05-03 17:50 ` [PATCH 2/2] org-refile: optionally prefix refile targets with buffer name Sebastian Reuße
2017-05-03 20:30 ` [PATCH 1/2] org-refile: escape slashes only in headline of refile target Sebastian Reuße
2017-05-03 20:30 ` [PATCH 2/2] org-refile: optionally prefix refile targets with buffer name Sebastian Reuße
2017-05-03 20:33 ` Sebastian Reuße
2017-05-05 23:23 ` Kyle Meyer [this message]
2017-05-05 23:22 ` [PATCH 1/2] org-refile: escape slashes only in headline of refile target Kyle Meyer
2017-05-06 5:51 ` [PATCH 1/2] org-refile: Escape " Sebastian Reuße
2017-05-06 5:51 ` [PATCH 2/2] org-refile: Optionally prefix refile targets with buffer name Sebastian Reuße
2017-05-06 6:34 ` [PATCH 1/2] org-refile: Escape slashes only in headline of refile target Sebastian Reuße
2017-05-06 6:34 ` [PATCH 2/2] org-refile: Optionally prefix refile targets with buffer name Sebastian Reuße
2017-05-06 6:38 ` [PATCH 1/2] org-refile: Escape slashes only in headline of refile target Sebastian Reuße
2017-05-06 6:38 ` [PATCH 2/2] org-refile: Optionally prefix refile targets with buffer name Sebastian Reuße
2017-05-06 6:41 ` [PATCH 1/2] org-refile: escape slashes only in headline of refile target Sebastian Reuße
2017-05-06 16:07 ` Kyle Meyer
2017-05-06 19:04 ` [PATCH] ORG-NEWS: Update new features Sebastian Reuße
2017-05-06 20:19 ` Kyle Meyer
2017-05-07 10:04 ` Nicolas Goaziou
2017-05-06 6:44 ` [PATCH 1/2] org-refile: escape slashes only in headline of refile target Sebastian Reuße
2017-05-06 16:08 ` Kyle Meyer
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tw4ysxaq.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=seb@wirrsal.net \
/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/org-mode.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).