unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Lawrence <rwl@recursewithless.net>
To: Visuwesh <visuweshm@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Improving Emacs' iCalendar support
Date: Wed, 23 Oct 2024 11:15:35 +0200	[thread overview]
Message-ID: <875xpjp4co.fsf@ohm.mail-host-address-is-not-set> (raw)
In-Reply-To: <87a5eyug9t.fsf@gmail.com>

Hi Visuwesh,

Visuwesh <visuweshm@gmail.com> writes:

> It has been at least a couple years since I wrote this function so I
> don't remember the hurdles I faced when I wrote it very well but it
> perplexed me that there were no "public" functions that were geared
> towards parsing an ical file.  In retrospect, it would have been less
> confusing if these functions were "public" functions.  AFAIR, and this
> very well might not be true, the structure returned
> icalendar--read-element is not really documented anywhere which further
> added to the confusion.

Yes, I had the same feeling. I spent a while looking through
icalendar.el about six months ago, hoping I could find an appropriate
point to hook into it/extend it. But the private function names and lack
of documentation of the data structures eventually caused me to give up.
I couldn't figure out a good way to use it or patch it to do what I
wanted, and it seemed like there were a lot of things it didn't
implement anyway...thus this current project ;)

> That said, this function has been rock solid ever since I wrote it.
> Going by the ical files I have, it is working just fine since 2021.

Are you saying it would be important to you to preserve the "private"
API of icalendar.el? or just that you're glad this API is still working? 

Best,
Richard



  reply	other threads:[~2024-10-23  9:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18  9:01 Improving Emacs' iCalendar support Richard Lawrence
2024-10-18  9:24 ` Eli Zaretskii
2024-10-19  8:22   ` Richard Lawrence
2024-10-19 10:11     ` Eli Zaretskii
2024-10-20  5:08       ` Richard Lawrence
2024-10-20  5:21         ` Eli Zaretskii
2024-10-18 12:58 ` Sebastián Monía
2024-10-19  8:28   ` Richard Lawrence
2024-10-19  5:44 ` Adam Porter
2024-10-19  8:39   ` Richard Lawrence
2024-10-20  3:09     ` Adam Porter
2024-10-22 18:40     ` Ihor Radchenko
2024-10-23  7:29       ` Björn Bidar
     [not found]       ` <87plnr6zvk.fsf@>
2024-10-23  8:09         ` Ihor Radchenko
2024-10-23  9:05         ` Richard Lawrence
2024-10-23 10:03           ` Björn Bidar
2024-10-23  9:01       ` Richard Lawrence
2024-10-23 20:24         ` Ferdinand Pieper
2024-10-21  6:10 ` Björn Bidar
2024-10-21  6:22 ` Visuwesh
2024-10-23  9:15   ` Richard Lawrence [this message]
2024-10-23  9:45     ` Visuwesh

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=875xpjp4co.fsf@ohm.mail-host-address-is-not-set \
    --to=rwl@recursewithless.net \
    --cc=emacs-devel@gnu.org \
    --cc=visuweshm@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
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).