From: jvinson@cheux.ecs.umass.edu (Jack Vinson)
Subject: Gnus-Topic ideas
Date: 30 Nov 1995 09:33:07 -0500 [thread overview]
Message-ID: <wowx8ip3z0.fsf@cheux.ecs.umass.edu> (raw)
Now that I have gnus topic working with v0.16, I'd like to make some
suggestions for more improvements. (Or should I say "more improvements to
this already excellent code?" :-)
- The documentation for the variable gnus-group-prepare-function needs to
be revised to not mention gnus-group-prepare-topics. Maybe the variable
should be eliminated completely, since the only value it can take is
'gnus-group-prepare-flat. Alternatively, if it is
'gnus-group-prepare-topics, then maybe the gnus topic mode should be
turned on automagically.
- gnus-topic-kill-group should mention that if you kill a topic that all
its groups will go as well. And when you yank it back, the groups come
with it.
- On a related note, there seems to be no easy way reorder topics at the
Gnus level. (Why is that level there, anyway?) For example:
Gnus
Alt
Emacs
Computers
Programming
Breaking
Misc
If I want to swap Comp and Emacs, how do I do it? If I kill and then
yank, the topic always gets inserted as a subtopic of the topic under the
cursor. Maybe a prefix argument to C-y to tell Gnus to insert the topic
at the same level as the current topic.
- Killed topics are never really removed. If I kill a topic and forget to
yank it back, it returns as the last Gnus subtopic. This is a good
thing, since it is the only way to rearrange topics at the Gnus level.
However, how would one remove a topic permanently? Removing it from the
gnus-group-topics should be a start.
- I'd like to see a way to go to the next topic via key strokes. It would
be nice to be able to jump between topics without having to hit n many
times. Maybe N to jump to next topic and P for previous topic. How
would this work with a full hierarchy? Prefix argument could tell it to
jump to a same-level topic, rather than the nearest neighbor.
--
( "Mmmmmm - coffee" (
)) Jack Vinson ))
C|~~| jvinson@cheux.ecs.umass.edu C|~~|
`--' `--'
next reply other threads:[~1995-11-30 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-30 14:33 Jack Vinson [this message]
1995-11-30 22:06 ` Steven L. Baur
1995-12-01 3:57 ` 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=wowx8ip3z0.fsf@cheux.ecs.umass.edu \
--to=jvinson@cheux.ecs.umass.edu \
/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).