all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: ics calendar?
Date: Fri, 08 Sep 2017 11:13:15 +0200	[thread overview]
Message-ID: <871snho8no.fsf@gmx.us> (raw)
In-Reply-To: CAN_Dec8fdUN7vEBdEVUjC4VuhkYq2+xsSrOY8nYFB=tSHsJjRw@mail.gmail.com

Matt Price <moptop99@gmail.com> writes:

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

1. Create the headline, "* Hacking History 2017 class {{{n}}}", maybe in a
   new file, classes.org.

2. Give it a date with "C-c .".  AFAIK you have to manually put the cursor
   on the new line.

3. M-x org-clone-subtree-with-time-shift and give
   (1- total-number-of-classes) plus a time shift, typically +1w-

4. Export to ICS, maybe as part of your publishing routine if ox-hugo uses
   ox-publish.

You should be able to create something like this,

* Hacking History 2017 class {{{n}}}
<2017-09-08 Fri 10:00-12:00>
* Hacking History 2017 class {{{n}}}
<2017-09-15 Fri 10:00-12:00>
* Hacking History 2017 class {{{n}}}
<2017-09-22 Fri 10:00-12:00>


I use org-caldav to synchronize with owncloud for what it is worth.

Hope it helps,
Rasmus

-- 
The right to be left alone is a human right

  parent reply	other threads:[~2017-09-08  9:14 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 [this message]
2017-09-08 15:52 ` Eric Abrahamsen
2017-09-11 13:45   ` Matt Price

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871snho8no.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.