From: Brian Sniffen <bts@evenmere.org>
To: David Mazieres expires 2021-04-20 PDT
<mazieres-3hcv6799u9einvp6psu79u6bce@temporary-address.scs.stanford.edu>
Cc: notmuch@notmuchmail.org
Subject: Re: What do people use for calendar invites?
Date: Thu, 21 Jan 2021 08:33:00 -0500 [thread overview]
Message-ID: <3076E67E-56CC-438F-B4E6-3A0379494C3A@evenmere.org> (raw)
In-Reply-To: <87mtx3quib.fsf@ta.scs.stanford.edu>
I don’t have an answer that lives in Emacs; I just let another imap client (Apple Calendar) read the mailbox for invitations and maintain my calendar. I just have to make sure getmail doesn’t delete the invitation messages.
--
Brian Sniffen
> On Jan 21, 2021, at 4:49 AM, David Mazieres <dm-list-email-notmuch@scs.stanford.edu> wrote:
>
> Calendar invites and the text/calendar mime type seem to be getting
> increasingly important. I asked about this five years ago and didn't
> get a good response, so I apologize for the repeat question, but I'm
> wondering if anything has changed since then.
>
> If you have found a good solution for integrating your calendar with
> notmuchmail, would you mind sharing what you are doing? Some specific
> questions:
>
> * What's a good way to generate text/calendar attachments from within
> notmuch (especially the emacs interface, which I use)?
>
> * What's a good way to apply text/calendar attachments to a calendar
> from within notmuch?
>
> * For those of us who hate gmail and love notmuch, but are still stuck
> using and hating google calendar, what alternative solutions should
> we be considering?
>
> Thanks,
> David
> _______________________________________________
> notmuch mailing list -- notmuch@notmuchmail.org
> To unsubscribe send an email to notmuch-leave@notmuchmail.org
next prev parent reply other threads:[~2021-01-21 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 17:33 What to people use for calendar invites? dm-list-email-notmuch
2015-05-22 15:30 ` Olivier Berger
2021-01-20 19:27 ` What do " David Mazieres
2021-01-21 13:33 ` Brian Sniffen [this message]
2021-01-21 14:37 ` David Bremner
2021-01-21 16:25 ` Jani Nikula
2021-01-22 18:02 ` Gregor Zattler
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3076E67E-56CC-438F-B4E6-3A0379494C3A@evenmere.org \
--to=bts@evenmere.org \
--cc=mazieres-3hcv6799u9einvp6psu79u6bce@temporary-address.scs.stanford.edu \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).