From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: question about org-link gnus message and gnus registry
Date: Thu, 02 Dec 2021 16:30:15 -0800 [thread overview]
Message-ID: <87v906zg14.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87k0gmmxps.fsf@web.de>
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> I'm still just seeing a call to `cl-second', which is required at
>> compile time. And my, there are a lot of compiler warnings! But nothing
>> about second or cl-second...
>
> This is where I found it:
>
> #+begin_src emacs-lisp
> (defun gnorb-reply-to-gnus-link (link)
> "Start a reply to the linked message."
> (let* ((link (org-link-unescape link))
> (group (car (org-split-string link "#")))
> (id (gnorb-bracket-message-id
> (second (org-split-string link "#"))))
> (backend
> (car (gnus-find-method-for-group group))))
> (gnorb-follow-gnus-link group id)
> (call-interactively
> (if (eq backend 'nntp)
> 'gnus-summary-followup-with-original
> 'gnus-summary-wide-reply-with-original))))
> #+end_src
Crap, it's in a commit I've had locally since... late 2020, but never
released. Sorry about that, I'll do another version release in a moment.
Thanks for finding this!
Eric
next prev parent reply other threads:[~2021-12-03 0:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 20:12 physiculus
2021-12-01 23:47 ` Bob Newell
2021-12-02 19:07 ` physiculus
2021-12-02 19:20 ` Eric Abrahamsen
2021-12-02 19:35 ` physiculus
2021-12-02 21:29 ` Eric Abrahamsen
2021-12-02 21:42 ` Michael Heerdegen
2021-12-02 21:44 ` Michael Heerdegen
2021-12-02 22:42 ` Eric Abrahamsen
2021-12-02 22:46 ` Michael Heerdegen
2021-12-03 0:30 ` Eric Abrahamsen [this message]
2021-12-03 1:50 ` Michael Heerdegen
2021-12-03 1:57 ` Eric Abrahamsen
2021-12-03 3:18 ` Eric Abrahamsen
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=87v906zg14.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=info-gnus-english@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.
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).