From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/7424 Path: main.gmane.org!not-for-mail From: John Griffith Newsgroups: gmane.emacs.gnus.general Subject: Re: Feature Request. Topic Group Parameters... Date: 02 Aug 1996 09:32:28 +0200 Sender: griffith@sfs.nphil.uni-tuebingen.de Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII X-Trace: main.gmane.org 1035147740 7194 80.91.224.250 (20 Oct 2002 21:02:20 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 21:02:20 +0000 (UTC) Cc: griffith@filippo.sfs.nphil.uni-tuebingen.de Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by deanna.miranova.com (8.7.5/8.6.9) with SMTP id BAA29576 for ; Fri, 2 Aug 1996 01:41:57 -0700 Original-Received: from filippo.sfs.nphil.uni-tuebingen.de (filippo.sfs.nphil.uni-tuebingen.de [134.2.129.45]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Fri, 2 Aug 1996 09:32:35 +0200 Original-Received: (from griffith@localhost) by filippo.sfs.nphil.uni-tuebingen.de (8.7.5/8.7.3) id JAA06453; Fri, 2 Aug 1996 09:32:29 +0200 (MET DST) Original-To: ding@ifi.uio.no In-Reply-To: Lars Magne Ingebrigtsen's message of 01 Aug 1996 22:49:48 +0200 Original-Lines: 39 X-Mailer: Gnus v5.2.37/XEmacs 19.14 Xref: main.gmane.org gmane.emacs.gnus.general:7424 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:7424 >>>>> "LMI" == Lars Magne Ingebrigtsen writes: LMI> How about looking at this in a different fashion -- use the LMI> display in a more active fashion. If I put point over g2 in LMI> t1 and execute some command, then it's obvious that I want to LMI> do something to that copy of g2, so g2 would inherit group LMI> parameters from the t1 topic. If I do the same command on LMI> the g2 copy in t3, then I would use the group parameters in LMI> the t3 topic. (And inheretance from parent topics, etc, LMI> naturally.) Ah, so you want different behavior depending which copy of the group you select. So you could have one copy of an nntp group in one topic with threading, and another copy in another topic without threading and with the `to-list' set to an alternative mail address. That sounds like a good idea, but some functions should be able to "stick" with a group wherever it goes. Like `auto-expire'. I guess you could say that if someone decides to read mail from their boss under a topic which has this set, then they should not be surprised when all read messages in that group expire. That's more the problem that a "home topic" was suppose to address. There should be some things about a group that don't change. You could force that information to be placed on the actual group itself, but that would remove the ability to create a topic for high-volume, low-content mailing lists and make them all `auto-expire' in one step. So the "home topic" idea was meant to determine parameters that you don't want to change. If you want some parameters to be "sticky", then you need a way of declaring them sticky (or maybe declaring a particular use of them sticky). There should be good (safe) defaults like `auto-expire' should be sticky, as well. -- John Griffith Seminar fuer Sprachwissenschaft, Universitaet Tuebingen email: griffith@sfs.nphil.uni-tuebingen.de www: