From: "Georg C. F. Greve" <greve@fsfeurope.org>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: R: Problems with iCalendar export of my Calendar
Date: Wed, 12 Nov 2008 11:49:02 +0100 [thread overview]
Message-ID: <87wsf9usm9.fsf@katana.lair> (raw)
In-Reply-To: <DC9E12C1-01E2-496A-82DC-789E58EADF87@uva.nl> (Carsten Dominik's message of "Tue, 11 Nov 2008 20:31:34 +0100")
[-- Attachment #1.1: Type: text/plain, Size: 1867 bytes --]
Hi Carsten,
On Tue, 11 Nov 2008 20:31:34 +0100
Carsten Dominik <dominik@science.uva.nl> wrote:
cd> A time-range with first an active stamp and then an inactive
cd> meaning has no defined purpose in Org, and I cannot say what will
cd> happen in what circumstances.
Understood.
Is there any reason why it has no defined purpose?
"Only display it on the first day and be silent on the others" seems
like an appropriate interpretation of the combination.
cd> You can get the un timed items first by configuring the variable
cd> `org-sort-agenda-notime-is-late'.
Thanks a lot - looks better already.
cd> That will not change the indentation though. Could be fixed, of
cd> course, that is a minor problem.
If it is not too big an issue, I'd very much appreciate the option to
have them displayed with proper indentation and without the (X/Y).
cd> One thing you can do is to set
cd> #+DRAWERS: dummy
cd> so that properties will not act as drawers anymore, so
cd> they will always be open and visible.
Thanks. That is a bit better.
cd> Properties? or dates? I happen to beliefe that there is no better
cd> input for times than those in Org.
And I happen to agree with you. One of the things in which or Org is
absolutely superior is entering or changing dates.
It is the properties that I generally found a bit cumbersome to deal
with, but maybe I'll just solve this with a small LISP function to take
care of the inserting of events, including property drawers and so on.
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
next prev parent reply other threads:[~2008-11-12 10:49 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
2008-11-11 19:31 ` Carsten Dominik
2008-11-12 10:49 ` Georg C. F. Greve [this message]
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=87wsf9usm9.fsf@katana.lair \
--to=greve@fsfeurope.org \
--cc=dominik@science.uva.nl \
--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).