emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bastien <bzg@gnu.org>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org, Greg Troxel <gdt@ir.bbn.com>
Subject: Re: observations on updating to recent org
Date: Wed, 23 Apr 2014 10:17:59 +0200	[thread overview]
Message-ID: <87a9bco3wo.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87lhuwmqr9.fsf@gmail.com> (Nicolas Goaziou's message of "Wed, 23 Apr 2014 09:47:22 +0200")

Hi Nicolas,

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Bastien <bzg@gnu.org> writes:
>
>> Nicolas, do you remember why we added IDs to all headlines and not
>> just the one that we be exported in the .ics file?
>
> It is a bit difficult to do otherwise.

Assuming this is just difficult, not impossible, what would be the way
to do it?

> We don't know beforehand what headlines are going to be exported.

Would it be possible to emulate export first just for the sake of
adding IDs where it's necessary?

> We get this information when a headline is encountered during
> export, which happens in a different buffer, and possibly in a
> different process.
>
> I think it is a minor inconvenience and we can live with it.

`org-icalendar-store-UID' is `nil' by default because a value of
`t' might be very inconvenient in some circumstances -- quoting the
docstring:

  "This variable is not turned on by default because we want to avoid
  creating a property drawer in every entry if people are only playing
  with this feature, or if they are only using it locally."

One way to adapt to the current behavior is to have a file dedicated
to being exported as an ics file -- but for people who want to export
entries from their regular files, having all those drawers created
everywhere just for the sake of a few entries being picked up for
the .ics output certainly feels wrong.

I'm interested in enhancing the current behavior if you can give me
a few directions.

Thanks,

-- 
 Bastien

next prev parent reply	other threads:[~2014-04-23  8:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-22 17:43 observations on updating to recent org Greg Troxel
2014-04-23  6:16 ` Bastien
2014-04-23  7:47   ` Nicolas Goaziou
2014-04-23  8:17     ` Bastien [this message]
2014-04-23 11:58       ` Nicolas Goaziou
2014-05-06  9:22         ` Bastien
2014-04-23 15:55 ` Greg Troxel
2014-04-23 16:16   ` Nicolas Goaziou
2014-04-23 16:25     ` Greg Troxel
2014-04-23 16:59       ` Nicolas Goaziou
2014-04-23 19:44         ` Nicolas Goaziou
2014-04-24 12:20           ` Greg Troxel

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=87a9bco3wo.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=gdt@ir.bbn.com \
    --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

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).