Re: [Orgmode] ido slow for outline path completion

[Carsten Dominik]

On Dec 21, 2008, at 10:24 PM, Samuel Wales wrote:

> Hi Carsten,
>
> I just meant that there are 3 path completion entry points
> (remember, which can also use refile; refile; and goto), and
> they are similar, but are specified differently
> (e.g. maxlevel variable in goto and alist in refile).  So,
> maybe there is a way to make the syntax for specifying them
> consistent for new users.
> Perhaps goto can use refile's path selection subsystem.
> That allows basename flex matching (by turning off
> org-refile-use-outline-path, useful for me as an interim workaround  
> for ido
> bugs) and other stuff like specifying the list of files to
> search.
Hi Samuel,

org-goto is different because it only goes to the
current file.  Refile was originally meant to
go to a selected class of headings.  You can use the refile
command itself including its setup to *go* some place
by calling org-refile with a prefix argument.  A double prefix
will make the command jump directly to the location where
the last refile event delivered its content.

- Carsten

> By the way, if you type "?" a few times using ido, it will
> show a completions buffer.  But here's the interesting part:
> that showed one path, which was "mytodo//" plus the full
> path name of the file -- not the outline path.  M might
> be another clue?
I have no time to debug ido, I am afraid, unless you can
show that the table I pass to ido is invalid.