Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: (provide 'nnmaildir)
Date: 28 Sep 2000 12:05:25 -0400	[thread overview]
Message-ID: <m37l7wmrhg.fsf@multivac.student.cwru.edu> (raw)
In-Reply-To: Paul Jarc's message of "14 Jul 2000 19:10:18 -0400"

<URL:http://multivac.cwru.edu/prj/nnmaildir.el>
feature: -wipe-on-delete
bugfix: -request-accept-article correctly finds end of a header
bugfix: Xrefs track changes in group names
bugfix: gnus-declare-backend is called

If you want messages and .nnmaildir files to be wiped on disk before being
deleted (this applies only to files with a single hard link), use a
select method like:
'(nnmaildir "whatever" (nnmaildir-wipe-on-delete t) ...)

There is a change in the .nnmaildir file format - Xrefs are generated
on the fly, and not stored in .nnmaildir.  But it seems Gnus tolerates
the extra garbage at the end of a NOV line, so you can just wait for
all your old .nnmaildir NOV lines to disappear with expiration.  You
can also fix your old .nnmaildir files with:
M-x replace-regexp RET C-q TAB Xref:[^ C-q TAB C-q C-j ]* RET RET
Or, if you don't care about losing marks, the usual: kill your
nnmaildir groups, exit Gnus, delete your .nnmaildir files, start Gnus
again and resubscribe.

Does anyone have a better way to wipe a file than this?
    (insert (format (concat "%" (number-to-string nchars) "s") ""))
    (write-region (point-min) (point-max) file)
After implementing this, I realized it might not do any good,
depending on how write-region works.  If it opens the file with
O_TRUNC, then I might be writing to different disk blocks than were
being used for this file's data before write-region opened it.  If
instead the file is opened (without O_TRUNC), written, and then
ftruncate'd, all is well.  Does anyone know which it is?

I still haven't figured out why -request-accept-article isn't seeing
that nnmaildir-filename is bound.  I've tried making it buffer-local
instead of bound by let; no dice.  It seems that -request-move-article
isn't even being called: I put in some message calls for debugging,
and nothing showed up in *Messages*.

What's the difference between gnus-summary-copy-article and
-crosspost-article?  Is the backend required to update a message's
Xref in either case?


paul



  parent reply	other threads:[~2000-09-28 16:05 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-14 23:10 Paul Jarc
2000-07-14 23:47 ` Steve Harris
2000-07-15  0:56   ` Paul Jarc
2000-07-16  1:14     ` Steve Harris
2000-07-16 12:44       ` Simon Josefsson
2000-07-17  2:43         ` Steve Harris
2000-07-17 18:28           ` Paul Jarc
2000-07-18  9:04             ` Kai Großjohann
2000-07-18 10:16             ` Simon Josefsson
2000-07-18 15:34               ` Steve Harris
2000-07-18 16:34                 ` Simon Josefsson
2000-07-18 16:48                   ` Kai Großjohann
2000-07-19 15:36                   ` Steve Harris
2000-07-20 14:19                     ` Paul Jarc
2000-07-24 20:10                       ` Paul Jarc
     [not found]                         ` <vafittodfig.fsf@lucy.cs.uni-dortmund.de>
2000-07-31 16:42                           ` Paul Jarc
2000-08-01 16:03                             ` Paul Jarc
2000-08-02 14:51                               ` Paul Jarc
2000-08-03 14:58                                 ` Paul Jarc
2000-08-04 15:44                                   ` Paul Jarc
2000-08-07 22:35                                     ` Paul Jarc
2000-08-11 15:01                                     ` Paul Jarc
2000-08-11 21:07                                       ` Kai Großjohann
2000-08-11 21:34                                         ` Paul Jarc
2000-08-13 16:08                                           ` Kai Großjohann
2000-09-04  3:51                                       ` Paul Jarc
2000-09-04  4:20                                         ` Paul Jarc
2000-09-04  8:26                                         ` Simon Josefsson
2000-09-05 18:49                                           ` Paul Jarc
2000-09-21 17:30                                         ` Paul Jarc
2000-09-21 21:30                                           ` Kai Großjohann
2000-09-21 22:43                                             ` Paul Jarc
2000-07-15  0:15 ` Simon Josefsson
2000-07-15  0:51   ` Paul Jarc
2000-07-15  1:21     ` Simon Josefsson
2000-07-15  1:24     ` Russ Allbery
2000-07-15 11:45     ` Kai Großjohann
2000-07-15 13:12       ` Simon Josefsson
2000-07-15 11:43 ` Kai Großjohann
2000-07-16 21:34   ` Paul Jarc
2000-07-16 21:47     ` Kai Großjohann
2000-07-17 18:17       ` Paul Jarc
2000-09-28 16:05 ` Paul Jarc [this message]
2000-09-28 18:46   ` Paul Jarc
2000-10-04 18:06 ` Paul Jarc
2000-10-04 18:21   ` Paul Jarc
2000-10-04 19:31     ` Simon Josefsson
2000-10-04 19:34       ` Paul Jarc
2000-10-04 19:52         ` Simon Josefsson
2000-10-04 20:32           ` Paul Jarc
2000-10-05  8:57             ` Simon Josefsson
2001-04-11 16:10 ` Paul Jarc
2001-04-15  3:57 ` Paul Jarc
2001-04-17  0:55 ` Paul Jarc
2001-04-24 15:11 ` Paul Jarc
2001-04-25 13:42   ` Paul Jarc

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=m37l7wmrhg.fsf@multivac.student.cwru.edu \
    --to=prj@po.cwru.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).