From: Ryan Thompson <rct@thompsonclan.org>
To: "David A. Gershman" <dagershman@dagertech.net>
Cc: Org-Mode List <emacs-orgmode@gnu.org>
Subject: Re: Lesson Learned: Day needed for iCalendar export
Date: Fri, 5 Mar 2010 14:54:41 -0800 [thread overview]
Message-ID: <2a4ba2fd1003051454w5b9dab36h7e7ef9d8f227a0b6@mail.gmail.com> (raw)
In-Reply-To: <20100228024907.5F128320056@mail.dagertech.net>
Without the day, the timestamp is not valid according to Org, so it
just treats it as normal text, or possibly something else entirely.
The real lesson is no to type timestamps manually. Use C-c <period>.
On Sat, Feb 27, 2010 at 6:49 PM, David A. Gershman
<dagershman@dagertech.net> wrote:
>
> Hello Everyone,
>
> I ran into this just now and I don't think it's documented anywhere so
> here is a tidbit thay may prevent some hair loss:
>
> I get a work calendar of my days off work for holidays. So I collect
> them in my .org file like so:
>
> * Work Holidays
> <2010-05-31>
> <2010-07-05>
> <2010-09-06>
> <2010-11-25>
> { there are more }
>
> When exporting my .ics file I found these dates were not showing up, but
> they *were* showing on my .org Agenda view. Turns out the iCalendar
> export needs the *day* also:
>
> * Work Holidays
> <2010-05-31 Mon>
> <2010-07-05 Mon>
> <2010-09-06 Mon>
> <2010-11-25 Thu>
>
> .ics export worked great after that. Enjoy!
>
> ----------------------------------------
> David A. Gershman
> gershman@dagertech.net
> http://dagertech.net/gershman/
> "It's all about the path!" --d. gershman
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
prev parent reply other threads:[~2010-03-05 22:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 2:49 Lesson Learned: Day needed for iCalendar export David A. Gershman
2010-03-05 22:54 ` Ryan Thompson [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=2a4ba2fd1003051454w5b9dab36h7e7ef9d8f227a0b6@mail.gmail.com \
--to=rct@thompsonclan.org \
--cc=dagershman@dagertech.net \
--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).