From: Tom Ed White <email@example.com>
To: Ihor Radchenko <firstname.lastname@example.org>
Cc: email@example.com, Tom Ed White <firstname.lastname@example.org>
Subject: Re: Unable to follow gnus links
Date: Mon, 04 Oct 2021 15:33:24 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <87zgrpb3k4.fsf@localhost> (Ihor Radchenko's message of "Mon, 04 Oct 2021 16:24:27 +0800")
Ihor Radchenko <firstname.lastname@example.org> writes:
> Tom Ed White <email@example.com> writes:
>> I was able to fix the problem for the time being by changing the
>> arguments to:
>> (defun org-gnus-open (path &rest _)
>> The keystroke I use is C-c C-o, which runs org-open-at-point which is in
> I understand. But it does not solve the potential problem for other users.
>> Debugger entered--Lisp error: (wrong-number-of-arguments (2 . 2) 1)
>> ... ((functionp (org-link-get-parameter type :follow)) (funcall
>> (org-link-get-parameter type :follow) path))
> Judging from your backtrace, you seem to have a mixed Org installation
> with some files loaded from Org <9.4 (that's when we changed the number
> of arguments in :follow functions).
> Can you try to re-install Org?
> Note that mixed installation can also cause other unexpected problems.
That was it, thank you. I was loading an obsolete version of
ol.el. Hopefully I've found and eliminated all obsolete org code.
prev parent reply other threads:[~2021-10-04 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 17:55 Unable to follow gnus links Tom Ed White
2021-10-03 8:35 ` Ihor Radchenko
2021-10-03 15:54 ` Tom Ed White
2021-10-04 8:24 ` Ihor Radchenko
2021-10-04 19:33 ` Tom Ed White [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).