Hello Bastien !
Thanx for testing !
Currently I think, that this function is most useful, if applied to all
org-buffers.
So I personally prefer the mulit-occur option, which gives me a list for all of
my org-buffers.
Therefore I feel a bit ashamed, that this does not work for you :-/
Did you get any errors ? Anything within the *Messages* Buffer ?
Is at least an *Occur*-Buffer created ?
A guess about a possible cause:
I assume that you alread use emacs 24, whereas I still cling to emacs 23.
Maybe some details of the contents of the created *Occur*-buffer has changed,
which might have broken my code (I found that I need to rely on the contents of
the *Occur*-buffer).
If you find that such an *Occur*-Buffer is created, when you run my function,
would it be possible to
send it to me ?
Thanx a lot !
with kind regards, Marc-Oliver Ihm
Am 18.07.2011 10:20, schrieb Bastien:
Hi Marc-Oliver,
Marc-Oliver Ihm<i...@online.de> writes:
I would like to submit the new function org-find-timestamps for
disussion.
Thanks for this piece of code and for this idea!
I've tested it a bit and I encourage others to test it.
I was able to create a sparse tree with inactive timestamps,
but I was not able to display a buffer with ordered items.
I will test more carefully and give feedback/debugging.
My main reaction is: your idea/code could partially sneak into
`org-sparse-tree' by adding a new ran[g]e option, asking the
starting and ending dates, and creating the sparse tree.
What do you think?
