Gnus development mailing list
 help / color / mirror / Atom feed
From: John Griffith <griffith@sfs.nphil.uni-tuebingen.de>
Cc: griffith@sfs.nphil.uni-tuebingen.de
Subject: Lots of Topics
Date: Tue, 19 Mar 1996 14:46:19 +0100	[thread overview]
Message-ID: <199603191346.OAA18250@filippo.sfs.nphil.uni-tuebingen.de> (raw)

I have a couple requests related to topic hierarchies.

1) I would like an option to only show topics if there is something
   unread-ish in it.

   Ie. 

   Topic0
     Topic1
       group1
     Topic2
     Topic3
       group2

   Do not show Topic2 here since there is nothing in it.  This could
   really cut out uninteresting screen clutter.  Of course this also
   requires a way to show all topics even if there isn't anything in
   them.

2) Many versions ago, I tried using a really large topic hierarchy.  I
   made a topic hierarchy from the first three levels of the Dewey
   Decimal Classification (between 900 and 1000 topics).  I added
   these to gnus-topic-topology and gnus-topic-alist, but I did not
   assign any groups to gnus-topic-alist (although I have worked on
   assigning the sci.* groups to DDC).  Anyway, what I noticed when I
   did that was that exiting groups and returning to the group buffer
   was extremely slow.  I have not checked the code to find out
   exactly what's going on and have not tried this in a few versions,
   but it seemed that the topic hierarchy was being rebuilt after
   exiting groups.  If this happens, is it necessary?

   If anyone wants, I can send them the DDC hierarchy.

3) What about non-unique names for topics?

   I realize this would require a new data structure to record paths
   in the topic hierarchy, but I at least would find it useful to use
   topic names more than once.  A simple example:

   Artificial Intelligence
      Programming Languages
         comp.lang.prolog
         comp.lang.lisp
   Information Systems
      Programming Languages
         comp.lang.java

   At this point the best one could do is something like:

   Artificial Intelligence
      Programming Languages - AI
         comp.lang.prolog
         comp.lang.lisp
   Information Systems
      Programming Languages - Info Sys
         comp.lang.java
  
4) What about "linked" topics?

   Ie. topic graphs rather than topic trees.  Then you could have
   symmetric topics like:

   Artificial Intelligence
      Programming Languages    [a]
   Information Systems
      Programming Languages    [b]
   Programming Languages
      Artificial Intelligence  [a]
      Information Systems      [b]

   where "Artificial Intelligence:Programming Languages" is the same
   set of groups as  "Programming Languages:Artificial Intelligence".


             reply	other threads:[~1996-03-19 13:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-03-19 13:46 John Griffith [this message]
1996-03-19 16:47 ` David C Worenklein
1996-03-19 19:38   ` David C Worenklein
1996-03-19 20:55 ` 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=199603191346.OAA18250@filippo.sfs.nphil.uni-tuebingen.de \
    --to=griffith@sfs.nphil.uni-tuebingen.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).