emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Georg C. F. Greve" <greve@fsfeurope.org>
To: Giovanni Ridolfi <giovanni.ridolfi@yahoo.it>
Cc: emacs-orgmode@gnu.org
Subject: Re: R: Problems with iCalendar export of my Calendar
Date: Tue, 11 Nov 2008 19:19:07 +0100	[thread overview]
Message-ID: <87od0mf7ms.fsf@katana.lair> (raw)
In-Reply-To: <860153.85437.qm@web28304.mail.ukl.yahoo.com> (Giovanni Ridolfi's message of "Tue, 11 Nov 2008 14:38:28 +0000 (GMT)")


[-- Attachment #1.1: Type: text/plain, Size: 2043 bytes --]

Hi Giovanni,

On Tue, 11 Nov 2008 14:38:28 +0000 (GMT)
Giovanni Ridolfi <giovanni.ridolfi@yahoo.it> wrote: 

 gr> Well, don't you like the "default" org-mode:
 gr> with the number of days (1/3)  ?

No, I think that is very annoying.

The only numbers I want to see there are times.

What I would want is something like this:

 Friday      7 December 2007
  abba:                   Gothenburg, Sweden 
  abba:       10:40-12:25 Flight SK 602 Zurich to Copenhagen 
  abba:       14:10-14:55 Flight SK 438 Copenhagen to Gothenburg 

where the "all day" or "time unspecific" events are listed on top
without any time, but properly indented, followed by all the timed
events in chronological order.


 gr> I think your org file should be structured better exploiting the
 gr> :PROPERTIES:

Thanks for the pointer.

Indeed it seems that properties can solve a significant amount of the
issues, although I had been avoiding them so far as I find them to
decrease the usability of the file.

When editing a calendar, it is very helpful to see the times and places
at first sight so you know that you don't have overlap or gaps.

If times are hidden in properties, that is much harder.

Also they are fairly cumbersome to edit.


 gr> appears quite clear to me: "The export will honor SUMMARY,
 gr> DESCRIPTION and LOCATION properties if the selected entries have
 gr> them.  If not, the summary will be derived from the headline, and
 gr> the description from the body (limited to
 gr> `org-icalendar-include-body' characters). "

That last part is interesting. It had indeed not occured to me that I
could set org-icalendar-include-body to 0 in order to avoid bogus
descriptions.

Regards,
Georg

-- 
Georg C. F. Greve                                 <greve@fsfeurope.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
President                                      +41 43 500 03 66 ext 400

Join the Fellowship and protect your freedom!     (http://www.fsfe.org)

[-- Attachment #1.2: Type: application/pgp-signature, Size: 306 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2008-11-11 18:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11 11:29 Problems with iCalendar export of my Calendar Georg C. F. Greve
2008-11-11 14:38 ` R: " Giovanni Ridolfi
2008-11-11 18:19   ` Georg C. F. Greve [this message]
2008-11-11 19:31     ` Carsten Dominik
2008-11-12 10:49       ` Georg C. F. Greve
2008-11-12 16:44         ` RFC 2445 compliance of org mode (was: Re: R: Problems with iCalendar export of my Calendar) Georg C. F. Greve

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=87od0mf7ms.fsf@katana.lair \
    --to=greve@fsfeurope.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=giovanni.ridolfi@yahoo.it \
    /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).