Gnus development mailing list
 help / color / mirror / Atom feed
From: Darek <darekce@gmail.com>
To: ding@gnus.org
Subject: Re: gnus-calendar fails to capture to org file
Date: Mon, 04 Nov 2024 18:53:50 +0100	[thread overview]
Message-ID: <87ttcm7ump.fsf@gmail.com> (raw)
In-Reply-To: <87h68ss7i0.fsf@gmail.com>

OK. Code is your friend. It turns out that in Gnus it works a bit
differently than in Mu4e. That's also fine.

On 2024/10/31 14:54, Darek <darekce@gmail.com> writes:

> Sending a reply works fine. Accepting an invitation opens buffers for
> all agenda files. I also have a *CAL* buffer filled with event data, but
> nothing is written to the org file. I configured the function according
> to the comments in gnus-icalendar.el.
>
> I used to use Mu4e and the capture worked fine. After switching to Gnus
> I lost this function.
>
> Unfortunately gnus-verbose=10 *Messages* does not log any errors.  I've
> exhausted all my ideas. How can I diagnose the problem?

-- 
Darek



      reply	other threads:[~2024-11-04 17:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31 13:54 Darek
2024-11-04 17:53 ` Darek [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

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

  git send-email \
    --in-reply-to=87ttcm7ump.fsf@gmail.com \
    --to=darekce@gmail.com \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).