From: Visuwesh <visuweshm@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Unexpected error using org-gnus-follow-link
Date: Thu, 12 Dec 2024 20:32:40 +0530 [thread overview]
Message-ID: <87y10lhrlb.fsf@gmail.com> (raw)
In-Reply-To: <874j39vz29.fsf@ucl.ac.uk> (Eric Fraga's message of "Thu, 12 Dec 2024 12:57:34 +0000")
[வியாழன் டிசம்பர் 12, 2024] Fraga, Eric wrote:
> Hello all,
>
> I upgraded both Emacs (from git) and org (elpa) in the last couple of
> days. Today I find that I get the following error using
> org-open-at-point:
>
> Debugger entered--Lisp error: (void-function nil)
> nil()
> org-gnus-follow-link("nnml+outlook:mail.dt2022" "[...]")
> org-gnus-open("nnml+outlook:mail.dt2022#[...]" nil)
> org-link-open((link (:standard-properties [1994 nil 2111 2179 2181 0 nil nil nil nil nil nil nil nil #<buffer todo.org> nil nil (paragraph (:standard-properties [1994 1994 1994 2182 2182 0 nil nil element t (3 . 1815) nil nil nil #<buffer todo.org> nil nil (item ...)]))] :type "gnus" :type-explicit-p t :path "nnml+outlook:mail.dt2022#[...]" :format bracket :raw-link "gnus:nnml+outlook:mail.dt2022#[...]" :application nil :search-option nil)) nil)
> org-open-at-point(nil)
> funcall-interactively(org-open-at-point nil)
> command-execute(org-open-at-point)
>
> with message reference elided.
>
> I cannot really reduce this to a minimal example or use -Q due to need
> to have gnus configured.
>
> Any suggestions on how to resolve this? The vast majority of my TODO
> entries have gnus email links and they have always worked just fine.
> The problem could, of course, be with gnus but I cannot tell from the
> above backtrace.
A shot in the dark after looking at org-gnus-follow-link: what is the
value of org-link-frame-setup? Does it have the gnus entry?
next prev parent reply other threads:[~2024-12-12 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 12:57 Unexpected error using org-gnus-follow-link Fraga, Eric
2024-12-12 15:02 ` Visuwesh [this message]
2024-12-12 18:15 ` Fraga, Eric
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y10lhrlb.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=emacs-orgmode@gnu.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/org-mode.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).