emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>, John Hendy <jw.hendy@gmail.com>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Inquiry about ical2org
Date: Fri, 27 May 2016 11:06:00 -0500	[thread overview]
Message-ID: <CA+M2ft8a_Cx__h1Kx-9SrU+cyH4EA3tJcVz=Ag0BRJV7H+uRTA@mail.gmail.com> (raw)
In-Reply-To: <8737p43pp2.fsf@ucl.ac.uk>

On Fri, May 27, 2016 at 2:50 AM, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> On Thursday, 26 May 2016 at 20:04, John Hendy wrote:
>
> [...]
>
>> Anyway, the point is that the repeater is built if there's any
>> repetition frequency/interval. You also capture the "until" into
>> rrend. So, the first date is going to feature a +unit, and this code
>> adds the end:
>>
>>         else if (rrend != "")
>>             date = date ">--<" rrend
>>
>> I just commented out both sections that add a "-- <date2>", the other
>> checking for time2 being "". Is that the correct way to go about this?
>
> Well, I would simply not add the end information as org does not
> understand an end date for a repeating item.  In other words, for a
> repeating item I would simply have the start date including the repeat
> directive.
>

Cool. Commenting has accomplished this for me and I don't get
repeating entries anymore.

>> Out of curiosity, how *is* the rrend code supposed to be handling
>> these? Or what's the use case for building a <date1 +unit>--<date2>?
>
> I should say that the awk codes have diverged.  My own version now
> differs significantly from what is on Worg, which is where I assume you
> got your copy.  I implemented repeating entries differently, it would
> seem.

Ah, that makes more sense. I was confused about agreeing that an end
date wasn't proper but the code having it. Is your original version
anywhere handy? I tried searching but don't seem to find it.


Thanks,
John

>
> HTH,
> eric
>
> --
> : Eric S Fraga (0xFFFCF67D), Emacs 25.0.94.1, Org release_8.3.4-869-gf2c421

  reply	other threads:[~2016-05-27 16:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <649f280c5d4d4c0b9f100fb9da170cdc@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-05-26  7:49 ` Inquiry about ical2org Eric S Fraga
2016-05-26 20:00   ` John Hendy
2016-05-26 20:04     ` John Hendy
2016-05-26 20:24     ` Ken Mankoff
     [not found]     ` <6aaed23035a1488b92c4c5b556966320@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-05-27  7:50       ` Eric S Fraga
2016-05-27 16:06         ` John Hendy [this message]
     [not found]         ` <82e201aa4dd34c99b527eb7b1009f062@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-05-30 12:59           ` Eric S Fraga
2016-05-25 20:33 John Hendy

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='CA+M2ft8a_Cx__h1Kx-9SrU+cyH4EA3tJcVz=Ag0BRJV7H+uRTA@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --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).