On Oct 29, 2009, at 8:56 PM, Harald Weis wrote:
But I still think it could be advantageous to do the whole lot within
the org-agenda-custom-commands variable if the match would be
evaluated
before getting used.
Well, we can try and see if it breaks something. The latest git version
now
Sorry, I was away for a couple of days.
Many thanks for your proposition which really works fine.
Still, would it be difficult to implement ``evaluating match before it
gets used''?
My user needs to define in his files a great number of
_multi-value_ property keys.
He also requires for an
Well, I guess I could evaluate match before it gets used. But maybe
you can also turn this around: Dinfe a function what will call the
tree maker directly
(defun my-tree (match)
(interactive s)
(org-match-sparse-tree nil (concat { match })))
or something like this
- Carsten
On
Hi All,
I would like to define one entry of the org-agenda-custom-commands
variable like so:
(setq org-agenda-custom-commands
'((i item tags-tree
(remedy-build-tags-tree-regex item
where ''item'' is the property key and
where the remedy-build-tags-tree-regex function is
hello org-mode users,
for some reason, my agenda export isn't working as it used to in the past.
(setq org-agenda-custom-commands '((x agenda export to html nil
(~/agenda.html
with this in my org configuration, i get 'x' as an accepted keystroke in the
agenda command selection buffer.
