From: Carsten Dominik <dominik@science.uva.nl>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: getting org-goto to work with ido
Date: Mon, 24 Nov 2008 10:59:21 +0100 [thread overview]
Message-ID: <AC480C14-D4CB-4413-BE46-378AC2C6CD52@uva.nl> (raw)
In-Reply-To: <20524da70811231313r147bcd6at5afbba6ce2f7a01f@mail.gmail.com>
Hi Samuel,
On Nov 23, 2008, at 10:13 PM, Samuel Wales wrote:
> Hi Carsten,
>
> Thanks for the release.
>
> ido.el works very well for org-refile.
>
> (setf org-refile-use-outline-path nil)
> (setq org-refile-targets '((org-agenda-files . (:maxlevel . 5))))
>
> org-goto does not work, but can be made to work.
>
> (setf org-goto-auto-isearch nil)
> (setf org-goto-interface 'outline-path-completion)
>
> To get it to work, I changed org.el's org-goto to remove the
> line that contains " (org-refile-use-outline-path t)".
What I don't like about this setup is that you may have similar
headlines in different places, and no way to see which is which.
If you pull the newest version, you have now an interesting alternative:
Restore the line in org-goto that you removed, and then do
(setq org-outline-path-complete-in-steps nil)
Then targets for org-goto will still be identified by their entire
path, in this way removing disambiguates, but you can then use
single-step completion to match the entire path, using ido if you wish.
By setting the variable, you will get the same interface in org-refile,
if you set org-refile-use-outline-path back to t.
Wow, this is *really* fast.
Maybe we should phase out the old org-goto interface that uses outline
drilling.
Maybe I should start by setting the default for org-goto-interface to
outline-path-completion.
Any thoughts about such a change?
- Carsten
next prev parent reply other threads:[~2008-11-24 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 21:13 getting org-goto to work with ido Samuel Wales
2008-11-24 9:59 ` Carsten Dominik [this message]
2008-11-25 20:07 ` Samuel Wales
2008-11-25 22:39 ` Carsten Dominik
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=AC480C14-D4CB-4413-BE46-378AC2C6CD52@uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@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 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).