From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/11526 Path: main.gmane.org!not-for-mail From: Hrvoje Niksic Newsgroups: gmane.emacs.gnus.general Subject: Re: Gnus v5.4.62 is released Date: 08 Jul 1997 22:49:34 +0200 Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035151222 30883 80.91.224.250 (20 Oct 2002 22:00:22 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 22:00:22 +0000 (UTC) Return-Path: Original-Received: from sandy.calag.com (root@sandy [206.190.83.128]) by altair.xemacs.org (8.8.6/8.8.6) with ESMTP id OAA12430 for ; Tue, 8 Jul 1997 14:41:15 -0700 Original-Received: from xemacs.org (xemacs.cs.uiuc.edu [128.174.252.16]) by sandy.calag.com (8.8.6/8.8.6) with ESMTP id OAA15868 for ; Tue, 8 Jul 1997 14:38:41 -0700 Original-Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by xemacs.org (8.8.5/8.8.5) with SMTP id QAA25571 for ; Tue, 8 Jul 1997 16:37:46 -0500 (CDT) Original-Received: from jagor.srce.hr (hniksic@jagor.srce.hr [161.53.2.130]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Tue, 8 Jul 1997 22:51:24 +0200 Original-Received: (from hniksic@localhost) by jagor.srce.hr (8.8.6/8.8.6) id WAA25483; Tue, 8 Jul 1997 22:49:34 +0200 (MET DST) Original-To: ding@ifi.uio.no X-Attribution: Hrv X-Face: Mie8:rOV<\c/~z{s.X4A{!?vY7{drJ([U]0O=W/xDi&N7XG KV^$k0m3Oe/)'e%3=$PCR&3ITUXH,cK>]bci&Ff%x_>1`T(+M2Gg/fgndU%k*ft [(7._6e0n-V%|%'[c|q:;}td$#INd+;?!-V=c8Pqf}3J In-Reply-To: Jens Lautenbacher's message of "08 Jul 1997 20:30:00 +0200" X-Mailer: Gnus v5.4.59/XEmacs 20.3(beta11) - "Stockholm" Original-Lines: 48 Original-Xref: altair.xemacs.org dgnus-list:1916 Xref: main.gmane.org gmane.emacs.gnus.general:11526 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:11526 Jens Lautenbacher writes: > > 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. > > Disk space? 100k+? even 300k wouldn't matter. So we differ. > You can't be serious suggesting that it's a user friendly behaviour to > need one time something like 10 A T I didn't say that. I just implied that you /can/ get the listing, even with `gnus-read-active-file' so `some'. > > > But it's extremely non-logical if suddenly I can't access the whole > > > feed anymore (...) > > > > Sure you can -- see above. > > No you can't; see above. What is this? A word game? > In some moon reader it's one keystroke to get all groups. Then we should make it so in Gnus, if you consider it important. Or back out this change -- because it's already been done, you know. > I don't care as a user if the program caches this list or not if > it's only fast enougth. The reason that tin can just forget about > all this is that it spends almost no time with parsing, while > gnus.... Well, there you have it -- and that was the exact reason to change for `gnus-read-active-file' to default to `some'. Maybe Gnus should read the whole active file the first time it starts up, and save the killed list for future usage? The obnoxious disk space usage still remains, but I guess noone really cares these days. -- Hrvoje Niksic | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- `VI' - An editor used by those heretics that don't subscribe to the Emacs religion.