From: Jens Lautenbacher <jtl@tkm.physik.uni-karlsruhe.de>
Subject: fix(?) and questions [sgnus-0.17]
Date: Sun, 3 Dec 1995 17:44:50 +0100 [thread overview]
Message-ID: <"nz11.rz.un.726:03.12.95.16.47.05"@rz.uni-karlsruhe.de> (raw)
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 <jtl@tkmhp12.physik.uni-karlsruhe.de>
+
+ * 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 <jtl@tkm.physik.uni-karlsruhe.de>
* gnus-topic.el (gnus-topic-update-topic): parameter `group' in
next reply other threads:[~1995-12-03 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-12-03 16:44 Jens Lautenbacher [this message]
1995-12-04 1:51 ` Lars Magne Ingebrigtsen
1995-12-04 9:46 ` Thomas Neumann
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='"nz11.rz.un.726:03.12.95.16.47.05"@rz.uni-karlsruhe.de' \
--to=jtl@tkm.physik.uni-karlsruhe.de \
/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).