From: "Fraga, Eric" <e.fraga@ucl.ac.uk>
To: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Unexpected error using org-gnus-follow-link
Date: Thu, 12 Dec 2024 12:57:34 +0000 [thread overview]
Message-ID: <874j39vz29.fsf@ucl.ac.uk> (raw)
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:
--8<---------------cut here---------------start------------->8---
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)
--8<---------------cut here---------------end--------------->8---
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.
Thank you,
eric
--
: Eric S Fraga, with org 9.7.17-3ae179 in Emacs 31.0.50
next reply other threads:[~2024-12-12 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 12:57 Fraga, Eric [this message]
2024-12-12 15:02 ` Unexpected error using org-gnus-follow-link Visuwesh
2024-12-12 18:15 ` Fraga, Eric
2024-12-13 5:42 ` Visuwesh
2024-12-13 10:46 ` Fraga, Eric
2024-12-15 16:41 ` Max Nikulin
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=874j39vz29.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).