From: Matt Lundin <mdl@imapmail.org>
To: "Jorge A. Alfaro-Murillo" <jorge.alfaro-murillo@yale.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Agenda to iCal not working
Date: Tue, 27 Oct 2015 20:25:49 -0500 [thread overview]
Message-ID: <87io5rss0y.fsf@fastmail.fm> (raw)
In-Reply-To: <87lhaojnqb.fsf@yale.edu> (Jorge A. Alfaro-Murillo's message of "Tue, 27 Oct 2015 12:11:08 -0400")
jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo) writes:
> Ken Mankoff writes:
>
>> I'm using the examples from
>> https://www.gnu.org/software/emacs/manual/html_node/org/Exporting-Agenda-Views.html
>>
>> Specifically,
>>
>> (setq org-agenda-custom-commands [...]
>
>>
>> But the HTML, PS, and ICS files are not being created. If I'm
>> visiting an Org file and run (org-icalendar-export-to-ics) then the
>> ICS is generated.
>>
>> Can someone offer advice why the ICS isn't generated when I generate
>> a specific agenda view?
>
> Setting up the agenda custom commands is not related to ical export.
In fact, it is. From the manual linked to in the original post:
"The extension of the file name determines the type of export. If it is
.html, Org mode will use the htmlize.el package to convert the buffer to
HTML and save it to this file name. If the extension is .ps,
ps-print-buffer-with-faces is used to produce Postscript output. If the
extension is .ics, iCalendar export is run export over all files that
were used to construct the agenda, and limit the export to entries
listed in the agenda. Any other extension produces a plain ASCII file."
Matt
next prev parent reply other threads:[~2015-10-28 1:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 13:46 Agenda to iCal not working Ken Mankoff
2015-10-27 16:11 ` Jorge A. Alfaro-Murillo
2015-10-28 1:25 ` Matt Lundin [this message]
2015-10-28 16:05 ` Jorge A. Alfaro-Murillo
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=87io5rss0y.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=emacs-orgmode@gnu.org \
--cc=jorge.alfaro-murillo@yale.edu \
/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).