Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai Grossjohann <grossjohann@amaunet.cs.uni-dortmund.de>
Subject: [Q] Enter a group, show an article -- how to?
Date: 24 Jul 1998 18:40:46 +0200	[thread overview]
Message-ID: <87ogufw6b5.fsf@slowfox.do.uunet.de> (raw)

Given a group name and an article number, I would like to enter this
group ephemerally and show exactly the given article plus the thread
that contains this article.

I am now doing the following:

,-----
| (gnus-group-read-ephemeral-group
|  GROUP                     
|  BACKEND                   
|  t                                  ; activate
|  (cons (current-buffer)    
|        'summary)                    ; window config
|  nil)                      
| (gnus-summary-limit (list ARTICLE-NUMBER))
| (gnus-summary-refer-thread)
`-----

This has a few problems, though.  For one thing, it is slow for large
groups, as it has got to fetch all article headers (not much of a
problem) and generate the complete summary buffer (this is the
time-killer, right here!) before throwing most of it away.  Is there a
way that I can enter the group without generating a huge summary
buffer first?  (Or should I wait for a new Gnus version which will
have a command for entering a group and displaying a specified set of
articles?)

The second problem with the above code is that it will ask the user
how many articles to receive, if the group is large.  An obvious
workaround is to temporarily bind gnus-large-newsgroup.  But is this a
good solution, too?

Oh, and another question: is the variable gnus-current-select-method
the right way of finding out the backend that the current summary
buffer belongs to?

And yet another question: is the variable gnus-article-current the
right way of finding the current article number?  Does it point to the
article that is being shown in the *Article* buffer or to the article
under point?  If the former, how to I find out the latter?

How could I have found each or any of the above without asking?  I
tried the time-tried UTSL method but I was lacking understanding of
what was going on...

kai
-- 
You cannot fix a machine by just power-cycling it with no
understanding of what is going wrong.  (Tom Knight)


             reply	other threads:[~1998-07-24 16:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-24 16:40 Kai Grossjohann [this message]
1998-07-24 22:08 ` Lars Magne Ingebrigtsen

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=87ogufw6b5.fsf@slowfox.do.uunet.de \
    --to=grossjohann@amaunet.cs.uni-dortmund.de \
    /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).