Nicolas Goaziou writes:
> I think it would be less ambiguous to use ICALENDAR_UNTIL (or UNTIL),
> and apply RFC 5545:
Ah, that specifies it nicely, thanks (and that was what I was (trying
to) do with the patch). That would mean exporting the time as well as
the date for end times (and calling th
Toke Høiland-Jørgensen writes:
> Michael Brand writes:
>
>> When implementing this, consider also whether the END_DATE should be
>> an agenda entry on its own and of which kind, warning period etc. I
>> tried to make an example that shows this issue.
>
> Adding to this, as mentioned previously,
Nicolas Goaziou writes:
> I'm clearly no Agenda specialist. I thought a DEADLINE would end
> a repeated event already. If it's not the case, does it make sense to
> implement it too?
I consider DEADLINE, in our context, to mean "when my finished work will
be needed", and therefore "when to start
Michael Brand writes:
> When implementing this, consider also whether the END_DATE should be
> an agenda entry on its own and of which kind, warning period etc. I
> tried to make an example that shows this issue.
Adding to this, as mentioned previously, I interpret the iCal standard
to really pe
Hi Nicolas
On Wed, Jul 24, 2013 at 10:38 AM, Nicolas Goaziou wrote:
> I'm clearly no Agenda specialist. I thought a DEADLINE would end
> a repeated event already.
No, DONE shifts it to the repeat date and like this it will never end.
> If it's not the case, does it make sense to implement it to
Hello,
Toke Høiland-Jørgensen writes:
> Handling it in the agenda can be done by an exclusion function. I
> currently have this in my org-agenda-skip-function-global (along with
> another function to skip items after their END_DATE):
>
> (defun thj/skip-excluded ()
> "Skip agenda items on date
Nicolas Goaziou writes:
> I think EXCLUDE property is a good idea, but I may be renamed to
> ICALENDAR_EXCLUDE until it is also handled by Org Agenda, if it ever
> happens. It also needs to be documented in the manual.
Handling it in the agenda can be done by an exclusion function. I
currently h
Hello,
Toke Høiland-Jørgensen writes:
> I've been wanting to have support for exporting recurring events to iCal
> while limiting the number of repetitions, as well as excluding dates.
> The patch below is my attempt to add this functionality. However, I'm in
> doubt as to whether or not this is
Hi
I've been wanting to have support for exporting recurring events to iCal
while limiting the number of repetitions, as well as excluding dates.
The patch below is my attempt to add this functionality. However, I'm in
doubt as to whether or not this is the right way to go about it (parsing
dates
