From: Simon Thum <firstname.lastname@example.org>
To: Nicolas Goaziou <email@example.com>
Cc: Org Mode List <firstname.lastname@example.org>
Subject: Re: [ANN] e-icalendar back-end
Date: Mon, 12 Nov 2012 00:04:07 +0100 [thread overview]
Message-ID: <50A02EE7.email@example.com> (raw)
On 11/11/2012 10:12 PM, Nicolas Goaziou wrote:
> Simon Thum<firstname.lastname@example.org> writes:
>> just tested and it seems to work fine.
> Thanks for testing it.
>> A glitch: Unlike the other functions, I could not get
>> org-e-icalendar-export-current-agenda to auto-complete in M-x
> That's correct. `org-e-icalendar-export-current-agenda' isn't meant to
> be a command. It will be called internally by `org-agenda-write' ("C-x
> C-w" from an agenda buffer). Though, for now, it isn't since
> org-icalendar.el is still current icalendar back-end.
>> and it also did not produce meaningful results (empty icalendar).
> Make sure to call it from an agenda buffer. Also, you may want to check
> `org-e-icalendar-include-todo' variable if your agenda view only
> contains TODO entries.
>> What I'm missing is the ability to influence the amount of information
>> "diclosed" for a public calendar. But 'll hack on this myself and come
>> back eventually.
> You can tweak `org-e-icalendar-include-body' (i.e. set it to nil).
I saw there are some knobs but I'm looking for more felixble soultions,
e.g. sth like org-icalendar-verify-function. Also "body" suggests the
headline is kept, which is too much for simply indicating availability.
But for now I'm content to get my phone to grasp the ical...
next prev parent reply other threads:[~2012-11-11 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 23:48 [ANN] e-icalendar back-end Nicolas Goaziou
2012-11-05 12:38 ` Vincent Beffara
2012-11-05 13:06 ` Nicolas Goaziou
2012-11-11 21:59 ` Simon Thum
2012-11-11 21:12 ` Nicolas Goaziou
2012-11-11 23:04 ` Simon Thum [this message]
2012-11-11 22:10 ` Nicolas Goaziou
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).