emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Harald Weis <hawei@free.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-agenda-custom-commands
Date: Fri, 30 Oct 2009 08:17:45 +0100	[thread overview]
Message-ID: <9CE0A4E8-CA1E-43BE-AD60-9FA0B2D8EA0F@gmail.com> (raw)
In-Reply-To: <20091029195607.GA3764@pollux.local.net>


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 does evaluate it, but I have not yet introduced this into the
customize type - so you need to set the command list in Lisp for the
time being.

- Carsten


>
> Thank you very much indeed.
> Harald Weis
>
>
> On Mon, Oct 19, 2009 at 03:36:42PM +0200, Carsten Dominik wrote:
>> 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 Oct 18, 2009, at 4:43 PM, Harald Weis wrote:
>>
>>> 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 defined as  
>>> follows:
>>>
>>> (defun remedy-build-tags-tree-regex (propkey)
>>>    (concat propkey
>>> 	  "={"
>>> 	  (read-from-minibuffer (concat propkey " : "))
>>> 	  "}"))
>>>
>>> This would allow me to select the property value interactively.
>>>
>>> The org-make-tags-matcher function does not appreciate.
>>> ''C-c a'' yields
>>> i	item	: set of 2 commands
>>>
>>> Selecting ''i'' produces the following error message in the
>>> minibuffer.
>>> Wrong type argument: stringp, (remedy-build-tags-tree-regex "item")
>>>
>>> Is there a way to get the desired functionality?
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

- Carsten

      reply	other threads:[~2009-10-30  7:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18 14:43 org-agenda-custom-commands Harald Weis
2009-10-19 13:36 ` org-agenda-custom-commands Carsten Dominik
2009-10-29 19:56   ` org-agenda-custom-commands Harald Weis
2009-10-30  7:17     ` Carsten Dominik [this message]

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=9CE0A4E8-CA1E-43BE-AD60-9FA0B2D8EA0F@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=hawei@free.fr \
    /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).