From: Dave Abrahams <dave@boostpro.com>
To: ding@gnus.org
Subject: Re: Creating an ephemeral group for a single article?
Date: Tue, 27 Sep 2011 12:51:32 -0400 [thread overview]
Message-ID: <m2pqimylm3.fsf@pluto.luannocracy.com> (raw)
In-Reply-To: <87pqinxdif.fsf@lifelogs.com>
on Mon Sep 26 2011, Ted Zlatanov <tzz-AT-lifelogs.com> wrote:
> On Thu, 15 Sep 2011 16:32:52 -0400 Dave Abrahams <dave@boostpro.com> wrote:
>
> DA> on Wed Sep 14 2011, John Wiegley <jwiegley-AT-gmail.com> wrote:
>
>>> I'd like to write a function that I could call from, say, Org. It should take
>>> a Message-Id, and create an ephemeral group containing that one message, found
>>> by the same mechanism that uses gnus-refer-article-method -- so that it can
>>> find the message wherever it might be. And if it truly can't find the
>>> message, it should ding and say that.
>>>
>>> What I have now is a half solution, as it inserts the message into my INBOX
>>> summary:
>>> (defun gnus-goto-article (message-id)
>>> (gnus-summary-read-group "INBOX" nil t)
>>> (gnus-summary-refer-article message-id))
>
> DA> John, did you see
> DA> [[gnus:nntp%2BLocalNNTP:gmane.emacs.gnus.general#m2r53hslyd.fsf@pluto.luannocracy.com][this
> DA> article]]?
>
> That seems like a very useful function. Dave, can your version (or
> whatever works for the most cases) go into Gnus if there's nothing
> already in there?
Sure, feel free to take it... but it's still only a half-solution.
If Gnus would let me enter an empty group, it would be a full solution
pretty quickly, but I don't know how to code around Gnus' limitations in
that respect
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
prev parent reply other threads:[~2011-09-27 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 4:57 John Wiegley
2011-09-15 20:32 ` Dave Abrahams
2011-09-26 20:19 ` Ted Zlatanov
2011-09-27 16:51 ` Dave Abrahams [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=m2pqimylm3.fsf@pluto.luannocracy.com \
--to=dave@boostpro.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).