unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ulf Jasper <ulf.jasper@web.de>
To: Hugo Heagren <hugo@heagren.com>
Cc: emacs-devel@gnu.org
Subject: Re: ical feeds for diary: why does icalendar.el always import to a file?
Date: Sun, 20 Feb 2022 21:36:58 +0100	[thread overview]
Message-ID: <87y225gtqt.fsf@panama> (raw)
In-Reply-To: <87bkzej4st.fsf@heagren.com> (Hugo Heagren's message of "Thu, 10 Feb 2022 12:15:46 +0000")

Am 10.02.2022 um 12:15 (+0000) schrieb Hugo Heagren:

> 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?

IIRC the original reason that icalendar.el offers import to file only
was that it appeared to be sufficient.  It simply looked as if there was
no need to import to buffers.  If there is a use case that works better
with a buffer instead of a file then that is a good reason to add that
functionality.

Best,
ulf




      reply	other threads:[~2022-02-20 20:36 UTC|newest]

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

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=87y225gtqt.fsf@panama \
    --to=ulf.jasper@web.de \
    --cc=emacs-devel@gnu.org \
    --cc=hugo@heagren.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
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).