Gnus development mailing list
 help / color / mirror / Atom feed
From: Stainless Steel Rat <ratinox@ccs.neu.edu>
Subject: Re: jka-compr support?
Date: Wed, 8 Nov 1995 14:41:43 -0500	[thread overview]
Message-ID: <199511081941.OAA15769@delphi.ccs.neu.edu> (raw)
In-Reply-To: Stephen Peters's message of Wed, 8 Nov 1995 11:19:14 -0800

X-Geek-3: GAT d-(++)@ s: a-
	C+(++) US++++$ P++>+++ L>+++ E+++ W++ N+++ K++++ w---$ O?>++ M-$ V-
	PS+ PE Y+(++) PGP++ !t 5++ X? R(+) tv b+++ DI+ D++ G+ e+>++(*) h! r y+
References: <199511080801.AA108837691@hpsdlgf8.sdd.hp.com>
	<199511081531.KAA29380@delphi.ccs.neu.edu>
	<199511081919.LAA23520@samsun.oracle.com>

-----BEGIN PGP SIGNED MESSAGE-----

jka-aux still won't help. The "problem" is that in order to speed things
up the backends do an 'ls' and store the output in a buffer. Gnus then
proceeds to pull filenames out of that buffer to do things like build
lists of files to actually delete. None of the jka-* stuff is hooked
into the buffer-manipulation routines (nor should it be), therefore none
of it is ever called, and if you compress your nnml or nnmh files
they'll never be removed from the disk because the backends will never
find them.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAwUBMKEH8J6VRH7BJMxHAQErUQQApH7KU9jG2GupQY7hgvDn3SxG5TQ9yLy+
5G2ZEgofKTAPP7sLpZKkR3RieUyh5rxhA3+u+Kek1tTqatoUn1dNar/GoKCYldcM
UyqNegiluxj0ot/JWL24qy1U1tPt4k32Ygz9Kd3Qeyyko/Ma5i1KI+oMSsnXSvK7
AyF18cBJius=
=ONAM
-----END PGP SIGNATURE-----

-- 
Rat <ratinox@ccs.neu.edu>          \ Caution: Happy Fun Ball may suddenly
PGP Public Key: Ask for one today!  \ accelerate to dangerous speeds.
http://www.ccs.neu.edu/home/ratinox/ \ 


             reply	other threads:[~1995-11-08 19:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-11-08 19:41 Stainless Steel Rat [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-11-08  8:01 Dave Disser
1995-11-08 15:31 ` Stainless Steel Rat
1995-11-08 19:19   ` Stephen Peters
1995-11-08 21:52     ` Steven L. Baur
1995-11-09 19:46       ` Scott Blachowicz

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=199511081941.OAA15769@delphi.ccs.neu.edu \
    --to=ratinox@ccs.neu.edu \
    /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).