From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/4236 Path: main.gmane.org!not-for-mail From: Jens Lautenbacher Newsgroups: gmane.emacs.gnus.general Subject: fix(?) and questions [sgnus-0.17] Date: Sun, 3 Dec 1995 17:44:50 +0100 Message-ID: <"nz11.rz.un.726:03.12.95.16.47.05"@rz.uni-karlsruhe.de> NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035145011 28917 80.91.224.250 (20 Oct 2002 20:16:51 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 20:16:51 +0000 (UTC) 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 JAA16357 for ; Sun, 3 Dec 1995 09:58:57 -0800 Original-Received: from nz11.rz.uni-karlsruhe.de (nz11.rz.uni-karlsruhe.de [129.13.64.7]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Sun, 3 Dec 1995 17:47:24 +0100 Original-Received: from tkmhp1.physik.uni-karlsruhe.de (actually tkmhp12.physik.uni-karlsruhe.de) by nz11.rz.uni-karlsruhe.de with SMTP (PP); Sun, 3 Dec 1995 17:46:58 +0100 Original-Received: by tkmhp1.physik.uni-karlsruhe.de (1.38.193.4/16.2) id AA01305; Sun, 3 Dec 1995 17:44:50 +0100 Original-To: ding@ifi.uio.no Xref: main.gmane.org gmane.emacs.gnus.general:4236 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:4236 There is one more fix for today, but maybe it's more a dirty workaround than a real fix. It fixes an error that occures when leaving a group that was selected from the list of killed groups and topic-mode is active, because this group doesn't belong to any topic, naturally. I have some questions and sugestions, also: 1) It seems to be impossible to get rid of the root of the topic-tree (that topic labeled "Gnus" on startup). But this topic makes no sense. It would be (_very much_) better to allow for multiple roots. Why should anyone want to hide/show the whole tree? I think, this decision (if I want to see my newsgroups or if I don't) is made on entering sgnus. 2) Topic rearrangement doesn't work very good by now. One needs a key (perhaps shift-tab) for un-indenting a topic. Also the topics behave a little unexpected. They seem to jump to the end of the list, when they are taken back one level of indentation. I think they should arrange _befor_ the former parent (so with one keystroke they can be moved back again). 3) I am still not happy with the way the killed groups are handled. The main point is that it is IMHO to slow (just the building of the buffer). And the lack of the mouse-face (which according to lars was made to speed things up) hurts the nice and colorful outfit of the rest of the program. So I have to wishes that exclude each other. But maybe we could do the following: * first of all: It should be sufficient to build the buffer of killed groups one time. By now it just uses the group buffer and the contents is lost as soon as one goes back to his/her normal groups. * Perhaps it would be possible to use something similiar as topic-mode to browse the list of killed groups (LOKG) Just build the topics based on the usenet hirachy, say 3 or 4 levels deep. Browsing could be done oneline (one would need an additional list that holds just the `topics', and maybe a flag if there are real groups at this level already): Present the user the highest topics, and if he/she selects "comp", just the new info is prepared and inserted into the buffer. So we wouldn't be faster if one wants to open all topics down to the group level, but the time the user sits and waits without any interaction would be reduced in almost all cases. 4) I tried a little change in gnus-group-unsubscribe-group: I just removed the calls to (gnus-group-update-group group) (2 of them) which was a dramatic speedup on subscribing to killed groups. But I am not in the position to see the nasty sideeffects this (undoubtly) will have. Could you tell me, please? The reason I tried this is that I want `subscribing' do only very limited things: It should enter the group into my group-buffer so I can select it, if I want to. I think it should retrieve any more info later on actually entering the group. Please enlighten me, if this is impossible. 5) I think, gnus-group-goto-unread should be bound to nil while browsing the LOKG. It always takes forever if you leave a group and it searches around 8000 lines only to find that there is no more unread group. And finally: the dirty patch I told you about many lines of email ago: With best regards, jens *** gnus-topic.el~ Sun Dec 3 15:02:26 1995 --- gnus-topic.el Sun Dec 3 16:48:51 1995 *************** *** 371,379 **** (entries (gnus-topic-find-groups (car type))) (visiblep (eq (nth 1 type) 'visible))) ;; Insert the topic line. ! (gnus-delete-line) ! (gnus-topic-insert-topic-line ! (car type) visiblep (not (eq (nth 2 type) 'hidden)) level entries))) ;;; Topic mode, commands and keymap. --- 371,382 ---- (entries (gnus-topic-find-groups (car type))) (visiblep (eq (nth 1 type) 'visible))) ;; Insert the topic line. ! (if topic ! (progn ! (gnus-delete-line) ! (gnus-topic-insert-topic-line ! (car type) visiblep ! (not (eq (nth 2 type) 'hidden)) level entries))))) ;;; Topic mode, commands and keymap. *** ChangeLog~ Sun Dec 3 15:07:40 1995 --- ChangeLog Sun Dec 3 16:54:08 1995 *************** *** 1,3 **** --- 1,8 ---- + Sun Dec 3 16:49:58 1995 Jens Lautenbacher + + * gnus-topic.el (gnus-topic-update-topic-line): bombed out on exit + from a group that was selected from the list of killed groups + Sun Dec 3 15:03:02 1995 Jens Lautenbacher * gnus-topic.el (gnus-topic-update-topic): parameter `group' in