emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: programatically generate an agenda
Date: Mon, 15 Feb 2021 18:45:49 +0100	[thread overview]
Message-ID: <87a6s5usvm.fsf@m4x.org> (raw)
In-Reply-To: <m2ft1y4lql.fsf@andrew.cmu.edu>

[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]

On 2021-02-14 12:12, John Kitchin <jkitchin@andrew.cmu.edu> writes:

> If it is possible to set up what you want in an entry in
> org-agenda-custom-commands, then you can call it in a program like
> #+BEGIN_SRC emacs-lisp
> (org-agenda nil "w" nil)

This is what I ended up doing.

- set up an agenda view with only the current day and the events:

#+begin_src emacs-lisp
  ("d" "Daily schedule"
   ((agenda ""
            ((org-agenda-span 'day)
             (org-agenda-use-time-grid nil)
             (org-agenda-skip-function '(org-agenda-skip-entry-if 'scheduled))

- use it with org-agenda write, massaging the results a little

#+begin_src emacs-lisp
(defun as/get-daily-agenda ()
  "Return the agenda for the day as a string."
  (let ((file (make-temp-file "daily-agenda" nil ".txt")))
    (org-agenda nil "d" nil)
    (org-agenda-write file nil nil "*Org Agenda(d)*")
      (insert-file-contents file)
      (goto-char (point-min))
      (kill-line 2)
      (while (re-search-forward "^  " nil t)
        (replace-match "- " nil nil))

Thanks again for your suggestion.



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 528 bytes --]

      parent reply	other threads:[~2021-02-15 17:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-13 18:05 programatically generate an agenda Alan Schmitt
2021-02-14 17:12 ` John Kitchin
2021-02-15 13:26   ` Alan Schmitt
2021-02-15 17:45   ` Alan Schmitt [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:

  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=87a6s5usvm.fsf@m4x.org \
    --to=alan.schmitt@polytechnique.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \


* 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


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).