From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Feature Request. Topic Group Parameters...
Date: 01 Aug 1996 22:49:48 +0200 [thread overview]
Message-ID: <x6u3umrfrn.fsf@eyesore.no> (raw)
In-Reply-To: John Griffith's message of 01 Aug 1996 10:20:40 +0200
John Griffith <griffith@sfs.nphil.uni-tuebingen.de> writes:
> t1
> g1
> g2
> t2
> g1
> g3
> t3
> g2
[Analysis snipped. I basically agree with everything you said and I
think your conclusion is correct -- a "home topic" is the solution.]
How about looking at this in a different fashion -- use the display in
a more active fashion. If I put point over g2 in t1 and execute some
command, then it's obvious that I want to do something to that copy of
g2, so g2 would inherit group parameters from the t1 topic. If I do
the same command on the g2 copy in t3, then I would use the group
parameters in the t3 topic. (And inheretance from parent topics, etc,
naturally.)
This means that one can't in general say what
`(gnus-group-read-group "g2")' will do when called from an unknown
point, but user commands executed in a normal fashion would have
predictable outcomes.
This is certainly easy enough to implement, which is why I like it.
:-) It's also easy to understand, I think, and requires no extra
information from the user on what she considers the "home topic" of
the group to be.
--
"Yes. The journey through the human heart
would have to wait until some other time."
next prev parent reply other threads:[~1996-08-01 20:49 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
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 [this message]
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=x6u3umrfrn.fsf@eyesore.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).