From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-refile and ivy
Date: Sat, 23 Jan 2021 06:24:20 +1100 [thread overview]
Message-ID: <87eeicbwd2.fsf@gmail.com> (raw)
In-Reply-To: <87v9borhz4.fsf@gmail.com>
Gustavo Barros <gusbrs.2016@gmail.com> writes:
> On Fri, 22 Jan 2021 at 15:49, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>
>> Dear all org mode list readers,
>>
>> I have been trying to get to grips with org-refile. For some reason,
>> the completion mechanism (I use ivy generally but I have no idea what
>> org-refile actually tries to do/use) only shows me the current file name
>> if I have org-refile-targets set to nil. It doesn't show any top level
>> headlines to choose from which is what I would expect from the
>> documentation. Hitting RET to select the completion target given (file
>> name only) refiles to the end of the file which is not what I want.
>>
>> This is with org updated fairly recently but not quite up to
>> date. However, I've had this problem for a long time and don't use
>> org-refile as a result.
>>
>> Any suggestions welcome.
>
> I use org-refile with ivy, so I might share. If I recall correctly, the
> only thing that does not play well between the two is
> `org-outline-path-complete-in-steps`. My basic setup is the following:
>
> #+begin_src emacs-lisp
> (setq org-refile-targets
> '((org-agenda-files :maxlevel . 6)
> ;; 'nil' means consider headings of the current buffer
> (nil :maxlevel . 6)))
> (setq org-refile-use-outline-path 'file)
> (setq org-outline-path-complete-in-steps nil)
> #+end_src
>
> That should get you started. I personally like org-refile for its
> quickness, so I do some extra work to filter out candidates of this list
> and keeping only the frequent targets (with
> `org-refile-target-verify-function'). And if something atypical arises,
> I just go with kill-yank.
>
> Note however, on the relation of org-refile and ivy:
> https://orgmode.org/list/87tuvrj7ww.fsf@gmail.com/
>
I am using spacemacs, currently with helm, but have used it with ivy as
well and I have the following setup for my org-refile, which I find
works well for my purposes.
org-refile-allow-creating-parent-nodes 'confirm
org-refile-targets (quote ((nil :maxlevel . 3)
(org-agenda-files :maxlevel . 3)))
org-refile-use-outline-path t
which allows me to type some of the 'path' name (e.g. outline heading or
org file name) and it shows me appropriate candidates.
I don't know if there is some spacemacs helm/ivy setup which plays a
part here - it just works, so I've not looked any further.
org version reports 9.4.4
--
Tim Cross
next prev parent reply other threads:[~2021-01-22 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 15:49 org-refile and ivy Eric S Fraga
2021-01-22 17:37 ` Gustavo Barros
2021-01-22 19:24 ` Tim Cross [this message]
2021-01-25 8:40 ` Eric S Fraga
2021-01-25 12:12 ` Pankaj Jangid
2021-01-22 18:23 ` Pankaj Jangid
2021-01-25 8:29 ` Loris Bennett
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=87eeicbwd2.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@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.
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).