emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Viktor Rosenfeld <listuser36@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] ox-icalendar: fix handling of timestamps
Date: Sun, 11 Aug 2013 14:42:14 +0200	[thread overview]
Message-ID: <20130811124214.GA69042@kenny.local> (raw)
In-Reply-To: <87mwooznuk.fsf@gmail.com>

Hi Nicolas,

Nicolas Goaziou wrote:

> Hello,
> 
> Viktor Rosenfeld <listuser36@gmail.com> writes:
> 
> >   * ox-icalendar.el (org-icalendar-entry): Honor setting of
> >   `org-icalendar-with-timestamps' for timestamps on headlines
> >   and checkboxes.
> >
> >   The setting `org-icalendar-with-timestamps' was only applied
> >   to timestamps which do not appear on a heading or on a
> >   checkbox. E.g., with `org-icalendar-with-timestamps' set to
> >   'active, an heading containing an inactive timestamp on would
> >   be exported. This patch fixes this.
> 
> This would make icalendar back-end inconsistent with other back-ends,
> see `org-export-with-timestamps' docstring.
> 
> If inconsistency is desirable in this case, `org-icalendar-with-timestamps'
> docstring should clearly state it.

The docstring of `org-icalendar-with-timestamps' already states:

  This variable has precedence over `org-export-with-timestamps'.
  It can also be set with the #+OPTIONS line, e.g. "<:t".

I believe that inconsistency is desirable here. Consider the following
use case with three headlines:

* TODO An appointment in the future
<2013-08-12 So 09:00>
* DONE A note about an appointment in the past
[2013-08-10 Fr 09:00]
* WAIT A reminder how long I've been waiting for something [2013-08-10 Fr]

The previous behavior, with `org-icalendar-with-timestamps' set to
'active, was that the first and the last headlines were picked up (even
though the timestamp in the last headline is inactive). This was
unexpected because the two inactive timestamps are handled differently.
My expectation was that only the first headline should have been
exported. This is what my patch achieves.

(Putting timestamps on the heading is useful to me because then I can
see them in the agenda. Also, I often put timestamps on lines with
checkboxes. However, I do not want to see any of those in my calendar
when I export only active timestamps.)

Cheers,
Viktor

> 
> 
> Regards,
> 
> -- 
> Nicolas Goaziou
> 

  reply	other threads:[~2013-08-11 12:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-11  2:03 [PATCH] ox-icalendar: fix handling of timestamps Viktor Rosenfeld
2013-08-11  2:13 ` Aaron Ecay
2013-08-11 12:53   ` Viktor Rosenfeld
2013-08-15  7:55     ` Nicolas Goaziou
2013-08-11  7:30 ` Nicolas Goaziou
2013-08-11 12:42   ` Viktor Rosenfeld [this message]
2013-08-11 13:15     ` Nicolas Goaziou
2013-08-11 14:14       ` Viktor Rosenfeld
2013-08-11 15:09         ` Viktor Rosenfeld
2013-08-15  7:52           ` Nicolas Goaziou

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=20130811124214.GA69042@kenny.local \
    --to=listuser36@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    /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).