Gnus development mailing list
 help / color / mirror / Atom feed
From: steve@miranova.com (Steven L. Baur)
Subject: Re: Gnus-Topic ideas
Date: 30 Nov 1995 14:06:03 -0800	[thread overview]
Message-ID: <m268g1n4fo.fsf@diana.miranova.com> (raw)
In-Reply-To: jvinson@cheux.ecs.umass.edu's message of 30 Nov 1995 06:33:07 -0800

>>>>> "Jack" == Jack Vinson <jvinson@cheux.ecs.umass.edu> writes:

    Jack> Now that I have gnus topic working with v0.16, I'd like to
    Jack> make some suggestions for more improvements.  (Or should I
    Jack> say "more improvements to this already excellent code?"  :-)

Gnus topics is looking very nice.  I'd like to add the following
suggestions to Jack's.

- gnus-group-topics should be advisory only.  That is it should only
be applied to a group that has not previously been assigned a topic.
As it stands right now, it will override manual reorganization.  As a
bonus, this would make a good default method of assigning new groups
to topics.

- It would be nice to have a set of operations extended to work with
topics.
 * M-g is perhaps the most useful.
 * Narrow to topic (although that may be doable already with hooks).

- A topic should have an assigned score file, topic.SCORE.  In the
score file hierarchy, it should come just ahead of all.SCORE.

- You should be able to assign a face per topic.  All groups for that
topic will appear in that face in the group/topic buffer.  Now that
could look interesting. :-)

For the last two suggestions, it would be acceptable to have them
apply when showing the flat display if the implementation required
it.

-- 
steve@miranova.com baur


  reply	other threads:[~1995-11-30 22:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-11-30 14:33 Jack Vinson
1995-11-30 22:06 ` Steven L. Baur [this message]
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=m268g1n4fo.fsf@diana.miranova.com \
    --to=steve@miranova.com \
    /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).