emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: "Filippo A. Salustri" <salustri@ryerson.ca>, emacs-orgmode@gnu.org
Subject: Re: Re: manipulating the agenda from elisp?
Date: Fri, 8 Apr 2011 18:59:38 +0200	[thread overview]
Message-ID: <BC2053AF-6F16-4BD0-A2F7-4853E2A3470E@gmail.com> (raw)
In-Reply-To: <87bp0h2z80.fsf@norang.ca>


On 8.4.2011, at 05:34, Bernt Hansen wrote:

> "Filippo A. Salustri" <salustri@ryerson.ca> writes:
> 
>> Hi,
>> I'm thinking I might like to try some programming to do things to the
>> agenda from an elisp function.
>> I tried 'apropos agenda' but I didn't really see the kind of thing
>> I'm looking for.
>> What I'm hoping is for some way to iterate over each item in the
>> agenda, and be able to access the content of the item in some
>> structured way.
>> I think I've seen functions that can pull info like TODO state and
>> priority from the item under the cursor, so it's the iteration part
>> that I'm really interested in.
>> 
>> Any advice?
> 
> Hi Fil,
> 
> I just found the B f code to execute an arbitrary function on marked
> entries in the agenda.  Maybe this will help?
> 
> This following code visits the marked entries and just displays the
> heading for the task.
> 
> Mark multiple entries in the agenda with 'm' and then 'B f bh/test RET'
> should display the heading of each marked task in the *Messages* buffer.
> 
> --8<---------------cut here---------------start------------->8---
> (defun bh/test ()
>  (interactive)
>  (let* ((marker (or (org-get-at-bol 'org-marker)
> 		     (org-agenda-error)))
> 	 (buffer (marker-buffer marker))
> 	 (pos (marker-position marker)))
>    (with-current-buffer buffer
>      (if (org-mode-p)
> 	  (save-excursion
> 	    (goto-char pos)
> 	    (message "%s" (nth 4 (org-heading-components))))))))
> --8<---------------cut here---------------end--------------->8---

Also useful can be

      (org-entry-properties marker)

Kind of slow for *many* entries, but perfectly good for a limited number...

- Carsten

  parent reply	other threads:[~2011-04-08 16:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08  2:05 manipulating the agenda from elisp? Filippo A. Salustri
2011-04-08  3:34 ` Bernt Hansen
2011-04-08  3:53   ` Filippo A. Salustri
2011-04-08  5:00     ` Nick Dokos
2011-04-08 11:30       ` Filippo A. Salustri
2011-04-08 16:59   ` Carsten Dominik [this message]
2011-04-08 17:00     ` Filippo A. Salustri
2011-04-08 16:36 ` Bastien

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=BC2053AF-6F16-4BD0-A2F7-4853E2A3470E@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=salustri@ryerson.ca \
    /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).