From: Matt Price <moptop99@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: ics calendar?
Date: Mon, 11 Sep 2017 09:45:25 -0400 [thread overview]
Message-ID: <CAN_Dec_a9TQscC2MWP1VMjOZU9H5Vay1fugxSBGtpSVy8-Vo7g@mail.gmail.com> (raw)
In-Reply-To: <87efrhtcgm.fsf@ericabrahamsen.net>
[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]
On Fri, Sep 8, 2017 at 11:52 AM, Eric Abrahamsen <eric@ericabrahamsen.net>
wrote:
> Matt Price <moptop99@gmail.com> writes:
>
> > I've been using Kaushal's fantastic ox-hugo to build my course websites
> (see http://2017.hackinghistory.ca/ for one more or less finished
> example; slightly out of date and not-yet documented source files are on
> Github at
> > https://github.com/titaniumbones/Hacking-History/tree/2017). It's a
> great system and I love it.
> >
> > I've just noticed that Hugo supports .ics formats and thought it would
> be useful to have a calendar for the class. I've never done .ics exports in
> org -- I don't use the core calendar/agenda features very effectively --
> and am not sure
> > what the best way to do this would be. So I'm really just asking
> whether other people do ics exports and if so, how you structure the org
> source files and so forth.
>
> In addition to what others have said, I'll note that the export process
> "flattens" all entries with dates, so the structure of the org file
> itself matters less. Apologies if you already knew that...
>
> Eric
>
thanks to both of you for the hints -- I have my dates in the headlines
themselves for various reasons, so I think I have to write a quick export
filter to remove them from the ics output. Running a little short o ntime
for the start of class (!) but maybe in the next week or s; if I get it to
work I'll report back.
[-- Attachment #2: Type: text/html, Size: 2176 bytes --]
prev parent reply other threads:[~2017-09-11 13:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 14:18 ics calendar? Matt Price
2017-09-07 16:00 ` Eric S Fraga
2017-09-08 9:13 ` Rasmus
2017-09-08 15:52 ` Eric Abrahamsen
2017-09-11 13:45 ` Matt Price [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=CAN_Dec_a9TQscC2MWP1VMjOZU9H5Vay1fugxSBGtpSVy8-Vo7g@mail.gmail.com \
--to=moptop99@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).