Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Those groups levels again
Date: 13 Nov 1995 17:17:12 +0100	[thread overview]
Message-ID: <w8s91lkwktz.fsf@surt.ifi.uio.no> (raw)

I just can't decide what to do about those pesky group levels.  This
is what I'm currently thinking about:

1) The level can be in integer, like now, between 1 and 9 (by default)

2) The level can be a cons, where the car has the level and the cdr
has a, uhm, score.  Perhaps.

Now, if we had this, we could do some interesting things.  Like
`sort-by-level-and-then-score'.  Then all level 4 groups would come
before all level 5 groups (so that those really important groups comes
before those less important) but we could still have bubbling on the
"score" of the group -- inside each level.  So whenever I read a level
5 group, the score would rise, and the next time I sort, that group
would "rise".  But it would never "rise" above any level 4 groups.

One could also do display-oriented things based on this (perhaps in
conjuction with `gnus-topic'.  Each level gets its own topic, and so
on. 

This would all be totally backwards compatible, and it's rather easy
to implement.  And it doesn't bloat the .newsrc.eld file much.  (I
originally thought of floating point levels, but that would really
either massively bloat the .newsrc.eld file, or slow down .newsrc.eld
generation dramatically.  (We couldn't use just `prin1' as now.))

Whadda y'all think?

In other news, I've been fixing lots & lots & lost of September bugs,
so I think that might be heading towards being usable.  nnsoup also
seems to have started behaving after I slapped it about a bit.  So I
think I'll be documenting it now.

Expect a release tomorrow.

-- 
Home is where the cat is.


             reply	other threads:[~1995-11-13 16:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-11-13 16:17 Lars Magne Ingebrigtsen [this message]
1995-11-13 19:50 ` Stainless Steel Rat
1995-11-13 20:58   ` Felix Lee
1995-11-13 22:48   ` Lars Magne Ingebrigtsen
1995-11-13 23:06     ` Scott Blachowicz
1995-11-13 23:15     ` Stainless Steel Rat
1995-11-18  6:49       ` Lars Magne Ingebrigtsen
     [not found]         ` <gvx91lext3f.fsf@plymouth.pilgrim.umass.edu>
1995-11-19  7:43           ` Lars Magne Ingebrigtsen
1995-11-20 16:43           ` Jack Vinson
1995-11-13 20:19 ` Joe Hildebrand
1995-11-13 20:21 ` Janne Sinkkonen
1995-11-18  6:49   ` Lars Magne Ingebrigtsen
1995-12-04 20:22 ` nnmail-expiry-wait-function: broke, or how-to? Mark Borges
1995-12-04 21:29   ` Steven L. Baur
1995-12-04 22:35     ` Mark Borges
1995-12-05  9:55       ` Lars Magne Ingebrigtsen
1995-12-04 22:09   ` Robert Pluim
1995-12-04 22:43     ` Mark Borges
1995-11-13 21:24 Those groups levels again Stainless Steel Rat
2002-10-20 20:14 Unknown
2002-10-20 20:14 Unknown

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=w8s91lkwktz.fsf@surt.ifi.uio.no \
    --to=larsi@ifi.uio.no \
    /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).