From: Colin Rafferty <craffert@spspme.ml.com>
Subject: Re: Feature Request. Topic Group Parameters...
Date: 30 Jul 1996 18:16:50 -0400 [thread overview]
Message-ID: <ocru3up75f1.fsf@spssunp.spspme.ml.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 30 Jul 1996 22:27:55 +0200
Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
> Ken Raeburn <raeburn@cygnus.com> writes:
>>> Bob Cotton <bcotton@hierarc.com> writes:
>>>> I'd like to see group parameters associated with Topics...
>> How should that deal with a group that falls under two topics?
> Good questions. I'm beginning to wonder whether it's worth it to be
> able to have the same group in several topics. It leads to all sorts
> of difficulties and ambiguities.
I think that having topic parameters is worth losing the ability to have
groups in multiple topics. I have `gnus-topic-unique' set to nil, but I
haven't found any very interesting use for it (other than to see the
bugs that still exist in the article count).
By the way, what is the replacement variable for `gnus-topic-unique'? I
just noticed that it is no longer documented (and I set it to nil in my
.gnus).
--
Colin
next prev parent reply other threads:[~1996-07-30 22:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-22 21:22 Bob Cotton
1996-07-23 6:59 ` Lars Magne Ingebrigtsen
1996-07-30 2:35 ` Ken Raeburn
1996-07-30 20:27 ` Lars Magne Ingebrigtsen
1996-07-30 22:16 ` Colin Rafferty [this message]
1996-07-31 11:37 ` Lars Magne Ingebrigtsen
1996-07-31 2:34 ` Ken Raeburn
1996-07-31 10:37 ` Per Abrahamsen
1996-07-31 7:11 ` Wes Hardaker
1996-07-31 12:30 ` John Griffith
1996-07-31 19:29 ` Lars Magne Ingebrigtsen
1996-08-01 8:20 ` John Griffith
1996-08-01 20:49 ` Lars Magne Ingebrigtsen
1996-08-02 7:32 ` John Griffith
1996-08-02 17:54 ` Lars Magne Ingebrigtsen
1996-08-05 11:37 ` Kai Grossjohann
1996-08-06 20:54 ` 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=ocru3up75f1.fsf@spssunp.spspme.ml.com \
--to=craffert@spspme.ml.com \
--cc=craffert@ml.com \
/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).