Gnus development mailing list
 help / color / mirror / Atom feed
From: Erik Selberg <speed@cs.washington.edu>
Subject: Re: Found No Mail!
Date: Mon, 04 Dec 1995 09:24:48 PST	[thread overview]
Message-ID: <199512041724.JAA12937@wally.cs.washington.edu> (raw)

As I alluded in a previous post, it seems that sep. v17 is having
problems when a spool file exists, but is zero-length. Appended is a
patch which seems to be working. The gist is that if the buffer is
zero-length, continue anyway. Continuing just means entering a while
loop which quits upon (eobp), so it's a no-op; we just don't hit the
"Found No Mail!" error.

Incidentally, perhaps the "Found No Mail!" error should be renamed to
something more appropriate, such as "Error, unknown format! (possible
corrupted)." I don't think it's appropriate that ding report an error
when the spool file is zero-length.

*** nnmail.el   Mon Dec  4 09:09:19 1995
--- nnmail.el~  Mon Dec  4 08:52:56 1995
***************
*** 477,485 ****
  (defun nnmail-process-unix-mail-format (func)
    (let ((delim (concat "^" rmail-unix-mail-delimiter))
        start message-id content-length end skip head-end)
!     (if (and (not (eobp))
!           (not (and (re-search-forward delim nil t)
!                 (goto-char (match-beginning 0)))))
        ;; Possibly wrong format?
        (error "Found no mail!") 
        ;; Carry on until the bitter end.
--- 477,485 ----
  (defun nnmail-process-unix-mail-format (func)
    (let ((delim (concat "^" rmail-unix-mail-delimiter))
        start message-id content-length end skip head-end)
!     (if (not (and (re-search-forward delim nil t)
!                 (goto-char (match-beginning 0))))
        ;; Possibly wrong format?
        (error "Found no mail!") 
        ;; Carry on until the bitter end.





                 reply	other threads:[~1995-12-04 17:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=199512041724.JAA12937@wally.cs.washington.edu \
    --to=speed@cs.washington.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).