unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hugo Heagren <hugo@heagren.com>
To: emacs-devel@gnu.org
Subject: ical feeds for diary: why does icalendar.el always import to a file?
Date: Thu, 10 Feb 2022 12:15:46 +0000	[thread overview]
Message-ID: <87bkzej4st.fsf@heagren.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]

I use the emacs diary a lot, and have recently had to start using
several centralised online calendars, which provide ical feeds (for
work). It's on the todo list in icalendar.el (line 92) to allow
including these in the diary in the same manner as including other
files.

I had a look at implementing this, and it doesn't seem terribly
difficult. The problem is that all the functions for importing ical
data to the diary format (which is what the calendar, the diary and
org-mode all understand) write it to a file by default. So to include
a feed, one has to retrieve the feed into a buffer, import the current
(ical) buffer into a diary file, then include the diary file. This
works, but it seems expensive to write to disk only in order to
(immediately!) read again. It seems to me that it would be easier to
just import the data into a buffer and keep it there. Does anyone if
there was an original reason /not/ to do this?

Given an answer either way, I'll try to work up a patch with the right
method.

Blue skies, Hugo

             reply	other threads:[~2022-02-10 12:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 12:15 Hugo Heagren [this message]
2022-02-20 20:36 ` ical feeds for diary: why does icalendar.el always import to a file? Ulf Jasper

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bkzej4st.fsf@heagren.com \
    --to=hugo@heagren.com \
    --cc=emacs-devel@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.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).