Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Gnus v5.4.62 is released
Date: 08 Jul 1997 09:34:27 +0200	[thread overview]
Message-ID: <kigiuymhu9o.fsf@jagor.srce.hr> (raw)
In-Reply-To: Sudish Joseph's message of "08 Jul 1997 01:28:25 -0400"

Sudish Joseph <sj@eng.mindspring.net> writes:

> >> I beg to differ. from the beginners point it's still a bit difficult
> >> to set up a gnus environment.
> 
> > Exactly.  Which is why Gnus should provide the most palatable
> > behaviour by default.  And I still think this category includes /not/
> > creating 100K+ .newsrc.eld by default.
> 
> FWIW, I'm totally with Jens here.  
> 
> A lot of the listing/jumping/subscribing commands work off of the
> killed list, as does newsgroup name completion.
[...]
> I quickly learnt to set save-killed-list to t when I left OSU with
> it's small active file to a server with a reasonable number of
> groups.

With the new default of `gnus-read-active-file' to `some', the killed
list will never have been constructed in the first place.

> Finally, I do not understand why disk space is the critical resource
> in this instance.

I didn't say it was the "critical resource" -- it's only a matter of
well-behaving.  Programs that save such large files by default don't
look well-behaving to me.  YMMV.

A practical reason is that there are people trying to run Gnus in a
multiuser environment, where they have a quota.  The size of
.newsrc.eld can matter to them.

> OTOH, the thing about save-killed-list that annoys me most is the
> additional time taken to save .newsrc.eld.  We can address that in
> other ways than to default to not saving killed-list.

How?

> Since it's largest component is the list of killed groups, and since
> that list is changed infrequently, it could be split out to a
> separate file (which could even be loaded only on demand, if
> needed).

Here you have touched a separate issue, which is caching of
server-side data.  For instance, Gnus might be much more useful if it
cached things like newsgroups list, newsgroup descriptions, and even
XOVER info, locally (Netscape 4 newsreader caches XOVER).

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
* Vi is the God of editors.
* Emacs is the editor of Gods.


  reply	other threads:[~1997-07-08  7:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-07-06 15:24 Lars Magne Ingebrigtsen
1997-07-06 16:05 ` Hrvoje Niksic
1997-07-07  9:08   ` Lars Magne Ingebrigtsen
1997-07-07 21:14     ` Hrvoje Niksic
1997-07-07 23:15       ` Jens Lautenbacher
1997-07-07 23:52         ` Hrvoje Niksic
1997-07-08  1:28           ` Steven L Baur
1997-07-08  2:39           ` Jens Lautenbacher
1997-07-08  4:01             ` Hrvoje Niksic
1997-07-08  5:28               ` Sudish Joseph
1997-07-08  7:34                 ` Hrvoje Niksic [this message]
1997-07-08 16:56                   ` Sudish Joseph
1997-07-08 18:30               ` Jens Lautenbacher
1997-07-08 20:49                 ` Hrvoje Niksic
1997-07-10 18:16                   ` Lars Magne Ingebrigtsen
1997-07-07  8:51 ` Steven L Baur
1997-07-07 11:36   ` Lars Magne Ingebrigtsen
1997-07-07 21:13     ` Hrvoje Niksic
1997-07-07 23:56       ` Steven L Baur
1997-07-10 18:08         ` Lars Magne Ingebrigtsen
1997-07-13 23:25           ` Hrvoje Niksic
1997-07-18  3:12             ` Steven L Baur

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=kigiuymhu9o.fsf@jagor.srce.hr \
    --to=hniksic@srce.hr \
    /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).