From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Getting/setting group parameters/info from backends.
Date: 02 Jan 1997 16:18:38 +0100 [thread overview]
Message-ID: <m2loaccdgx.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: visigoth@naiad.fac.cs.cmu.edu's message of 29 Dec 1996 06:27:18 -0500
visigoth@naiad.fac.cs.cmu.edu writes:
> So--what I'd like to find is some method for a back-end to ask for
> and/or manipulate the group info at any point it wants to.
> Specifically, if that's a problem, I need access to read group-info
> -before- Gnus does an nnimap-request-group, because I need to have
> that number to calculate the results.
Why do you need to store that information in the group info? Most
other backends store information they need in separate files. I
realize that this may be a pain to do with IMAP, since that would make
things much less portable, but can't you store that in a special
folder on the IMAP server or something? (I know nothing about IMAP,
so just bonk me on the head if I'm raving here...)
> I'm not sure exactly how this should work. When a back-end asks for
> information, it somehow has to identify exactly the group it's asking
> for. What if two servers on one backend have the same group name?
The nntp backend just has `nntp-current-group' that says what the
current group is. The nnoo stuff will switch between various virtual
servers for you, so that's no problem.
> Can you have multiple servers connecting to one machine?
If you want to, I guess.
> The list appears to be down for now--but I look forward to input when
> it comes back up.
Has it been down? Eeek!
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
next prev parent reply other threads:[~1997-01-02 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-12-29 11:27 visigoth
1997-01-02 15:18 ` Lars Magne Ingebrigtsen [this message]
1997-01-02 20:50 ` visigoth
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=m2loaccdgx.fsf@proletcult.slip.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).