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

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)

In that snippet, I have the key in an org-agenda-custom-commands set to

that generates an agenda buffer for me, which I assume you can then use
the org-agenda-write command on.

Alan Schmitt <alan.schmitt@polytechnique.org> writes:

> Hello,
> In my quest/endeavor/struggle to generate an org file for what I want to
> do during the day, I’m trying to leverage the power of org-agenda (that
> does a lot of what I want to do) to create an org file. I learned of
> org-agenda-write, which I could use to write to file what I want then
> include it in my org file, but for that I need to create the correct
> org-agenda buffer. What is the elisp way of doing it?
> I tried using org-agenda-list, but it only seems to restore the current
> agenda view. For instance, (org-agenda-list nil nil 1) generates an
> agenda for the week (which is my default), even though I pass a SPAN
> argument of 1. I also don’t know how to set the org-agenda-skip steps
> before calling that function…
> Thanks a lot for any suggestion on how to do this.
> Best,
> Alan

Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213

  reply	other threads:[~2021-02-14 17:13 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 [this message]
2021-02-15 13:26   ` Alan Schmitt
2021-02-15 17:45   ` Alan Schmitt

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


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