From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 49995@debbugs.gnu.org, Pankaj Jangid <pankaj@codeisgreat.org>
Subject: bug#49995: 28.0.50; EBDB Anniversaries do not appear marked in calendar
Date: Wed, 18 Aug 2021 17:57:11 +0200 [thread overview]
Message-ID: <874kbmwxt4.fsf@web.de> (raw)
In-Reply-To: <87y28zua6h.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 17 Aug 2021 12:45:58 -0700")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Otherwise, `ebdb-diary-anniversaries' works the way it does now, for
> only the diary, or in Org.
Ok, great.
>
> Maybe, additionally, we provide a `ebdb-export-to-org' command that
> writes an Org file holding all our anniversaries as headings, with
> advance notifications implemented as DEADLINE lines with a warning
> period. [...]
While the idea has some charm, you would loose the speed advantages from
using a hash table for lookup, right? Or would Org build and use one
internally?
Anyway, I think personally I would not want to have a second place for
anniversaries - unless it would then be beneficial to use only that file
in the future.
> How does all of that sound?
All of that sounded good, thanks for your time.
Michael.
next prev parent reply other threads:[~2021-08-18 15:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 7:13 bug#49995: 28.0.50; EBDB Anniversaries do not appear marked in calendar Pankaj Jangid
2021-08-13 19:35 ` Eric Abrahamsen
2021-08-14 15:20 ` Michael Heerdegen
2021-08-14 18:08 ` Eric Abrahamsen
2021-08-15 4:01 ` Eric Abrahamsen
2021-08-15 13:18 ` Michael Heerdegen
2021-08-15 14:28 ` Eric Abrahamsen
2021-08-15 15:57 ` Eric Abrahamsen
2021-08-15 20:16 ` Eric Abrahamsen
2021-08-17 17:16 ` Michael Heerdegen
2021-08-17 19:45 ` Eric Abrahamsen
2021-08-18 15:57 ` Michael Heerdegen [this message]
2021-08-18 17:13 ` Eric Abrahamsen
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=874kbmwxt4.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=49995@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=pankaj@codeisgreat.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).