From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/3813 Path: main.gmane.org!not-for-mail From: Sudish Joseph Newsgroups: gmane.emacs.gnus.general Subject: Re: gnus-topic open-topic indicator Date: 02 Nov 1995 02:27:59 -0500 Organization: The Ohio State University Dept. of Computer and Info. Science Sender: joseph@cis.ohio-state.edu Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035144643 27378 80.91.224.250 (20 Oct 2002 20:10:43 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 20:10:43 +0000 (UTC) X-From-Line: ding-request@ifi.uio.no Thu Nov 2 01:01:27 1995 Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by miranova.com (8.6.11/8.6.9) with ESMTP id BAA06143 for ; Thu, 2 Nov 1995 01:01:25 -0800 Original-Received: from news.cis.ohio-state.edu (news.cis.ohio-state.edu [164.107.8.50]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Thu, 2 Nov 1995 08:52:07 +0100 Original-Received: from bank.cis.ohio-state.edu (bank.cis.ohio-state.edu [164.107.16.2]) by news.cis.ohio-state.edu (8.6.8.1/8.6.4) with ESMTP id CAA29270 for ; Thu, 2 Nov 1995 02:28:53 -0500 Original-Received: (joseph@localhost) by bank.cis.ohio-state.edu (8.6.7/8.6.4) id CAA17651; Thu, 2 Nov 1995 02:28:01 -0500 Original-To: The Ding List In-Reply-To: Dave Disser's message of 01 Nov 1995 22:39:22 -0800 Original-Lines: 30 Xref: main.gmane.org gmane.emacs.gnus.general:3813 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:3813 Dave Disser writes: > More on this... Maybe a gnus-topic-line-format is the righter thing > to do? Yes, please! I can see the eventual addition of unread/marked article totals (for subsumed groups) to the closed topic line in the group buffer; implementing it this way allows for future functionality. Another cool topics feature would be to allow interactive movement of groups between topics. I.e., we might overload Cut (C-k, C-w) and Paste (C-y) so that the group gets inserted into the topic it was yanked under. This isn't very hard, we just have to add an entry to the group parameter list at yank time. The only issue is how to specify it doesn't belong to another topic. For instance, you might have gnu.emacs.gnus under your `Emacs' topic (having been put there via gnus-group-topics rather than a group parameter), yanking this under your `Newsreaders' topics would leave a copy under the old topic. Not a big thing, but it would complicate (and/or seriously slow down) the update of read/ticked article counts (if they get added). Hmm, maybe add a parameter to indicate that the group should belong to just the one topic? Or just use the existence of a topic parameter to determine this (i.e., ignore gnus-group-topics for such groups)? Actually, the interaction between gnus-group-topics and group parameter entries should probably be settled before doing the above. -Sudish