emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] [PATCH 2/2] org-refile: optionally prefix refile targets with bu


From: Kyle Meyer
Subject: Re: [O] [PATCH 2/2] org-refile: optionally prefix refile targets with buffer name
Date: Fri, 05 May 2017 19:23:25 -0400

Sebastian Reuße <address@hidden> 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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]