From: Leo <sdl.web@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: Fetch an article from another package
Date: Mon, 26 Mar 2007 19:28:52 +0100 [thread overview]
Message-ID: <m28xdjyi3f.fsf@sl392.st-edmunds.cam.ac.uk> (raw)
In-Reply-To: <v9tzw9jx0q.fsf@marauder.physik.uni-ulm.de>
On 2007-03-25, Reiner Steib said:
> On Sun, Mar 25 2007, Leo wrote:
>
>> Org¹ mode uses the following function to open a Gnus link. However,
>> the downside it has when entering a large group is that Gnus will
>> prompt for how many articles to read. I'd like this function to just
>> get the article with minimal user interaction. It seems by changing
>> (gnus-group-read-group 0 nil group) to (gnus-group-read-group 1 nil
>> group) can solve this issue.
>>
>> I am wondering is this the recommended way? Any comments?
>>
>> ,----
>> | (defun org-follow-gnus-link (&optional group article)
>> | "Follow a Gnus link to GROUP and ARTICLE."
>
> I'd suggest to use the functions from `gnus-art.el' that handle
> buttons like <nntp://news.gmane.org/gmane.emacs.gnus.user/8816> or
> <nntp://news.gmane.org/gmane.emacs.gnus.user>:
[...]
> `gnus-large-ephemeral-newsgroup' might also be useful.
>
> Bye, Reiner.
The link is of the format: gnus:gmane.emacs.gnus.user#8816 it is then
parsed into two variables GROUP and ARTICLE and passed to
org-follow-gnus-link.
It seems gnus-button-fetch-group is not the right function for this
task and gnus-large-ephemeral-newsgroup does not help either.
Let me rephrase the question, I now have group name and article number
outside gnus, what's the best way to fetch that article?
Thanks,
--
Leo <sdl.web AT gmail.com> (GPG Key: 9283AA3F)
next prev parent reply other threads:[~2007-03-26 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 9:25 Leo
2007-03-25 13:03 ` Reiner Steib
2007-03-26 18:28 ` Leo [this message]
2007-03-26 20:56 ` Reiner Steib
2007-04-12 14:49 ` Leo
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=m28xdjyi3f.fsf@sl392.st-edmunds.cam.ac.uk \
--to=sdl.web@gmail.com \
--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).