On Mon, Dec 22, 2008 at 01:30, Carsten Dominik wrote:
>> 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
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
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
On Dec 19, 2008, at 12:57 AM, Samuel Wales wrote:
Hi Carsten,
On Mon, Dec 15, 2008 at 02:36, Carsten Dominik
wrote:
1. Compile Org! Are you using byte-compiled files?
In a case like this, the differences may be significant.
Always! :)
4. Create the list of headings with full outlin
Hi Samuel,
this is deep inside the ido routines, and I do not have enough
insight to see what is going on. Maybe send a bug report to Kim?
Maybe you can create a test case for him by capturing the table
before it is passed to the ido-complete command?
If it is really the length of the strings,
*** ido
Hi Carsten,
Thanks for looking at the speed issues.
This time an error showed up. The error from the messages
buffer is:
Getting targets...done
eq: Wrong type argument: arrayp, (#("footodo/...
The trigger is:
org-goto, same settings as before, searching for a headline called
"pars
Hi Carsten,
On Fri, Dec 19, 2008 at 01:39, Carsten Dominik wrote:
> Could you sent a test file for this? I cannot reproduce it.
My org agenda files take up 500kB (I think completion uses those?) and
I don't know what about them is causing this in order to create a test
case.
I wish there were
Hi Samuel,
However, when I do org-refile as full path (not basenames),
it sometimes takes 45 seconds.
Could you sent a test file for this? I cannot reproduce it.
- Carsten
I haven't narrowed it down yet. Emacs just freezes.
Every character I type from that point on takes another 45
se
Hi Carsten,
On Mon, Dec 15, 2008 at 02:36, Carsten Dominik wrote:
> 1. Compile Org! Are you using byte-compiled files?
>In a case like this, the differences may be significant.
Always! :)
> 4. Create the list of headings with full outline path
>in a single path of the file, similar to
Hi Samuel,
I am sure that both org and ido will contribute to a slow start
of this command when the lists are long. ido does have a noticeable
on performance, but that is more than outweighed by the speedup of using
its commands.
However, I believe the more significant problem may
be in Org in t
ido for refiling works very well and makes refiling easier
by orders of magnitude. Thank you Eric. Thank you Carsten.
In org 6.14, I find that full path completion (which is the
only way that org-goto can use ido) can take 22-45 seconds
before it shows you the prompt. This is on a 1ghz mac and
11 matches
Mail list logo
