* Re: Problem with .gnus.el
[not found] <m3671kf2k2.fsf@quicksilver.bzl.bzl>
@ 1999-09-09 6:13 ` Shenghuo ZHU
0 siblings, 0 replies; 4+ messages in thread
From: Shenghuo ZHU @ 1999-09-09 6:13 UTC (permalink / raw)
Cc: Gnus Mailing List, Lars Magne Ingebrigtsen
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
>>>>> "BZL" == Bruce Z Lysik <eldrik@quicksilver.bzl.bzl> writes:
BZL> Hi guys.
BZL> I decided to change my MTA, and went about installing qmail. Things
BZL> appeared to have went fine with the installation.
BZL> Next I wanted to make gnus read from my Maildir as a mail source. So
BZL> I stuck (setq mail-sources '((file) (maildir))) into my .gnus.el.
BZL> On starting up gnus I got the error: Wrong type argument:
BZL> integer-or-marker-p, nil
BZL> Thinking there's something wrong with my mail-sources, I comment it
BZL> out, and do what I think is setting my .gnus.el back to normal.
BZL> Unforunately I /STILL/ get the error. Kinda serious.
BZL> I turned on debug-on-exit. Here's the result of the backtrace when I
BZL> try to enter gnus:
I guess you got a bad mail which does not contain "\n\n" (maybe an
empty file). Anyway, I found a typo in
nnmail-process-maildir-mail-format. Hope this patch solve your
problem.
BTW, gnu.emacs.gnus is wrong place to post bug about pgnus. Send it
to ding@gnus.org.
Shenghuo
1999-09-09 Shenghuo ZHU <zsh@cs.rochester.edu>
* nnmail.el (nnmail-process-maildir-mail-format): Typo.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 96-zsh4.diff --]
[-- Type: text/x-patch, Size: 472 bytes --]
--- ../../pgnus-sent/lisp/nnmail.el Fri Aug 27 16:33:42 1999
+++ nnmail.el Thu Sep 9 01:58:59 1999
@@ -814,8 +814,8 @@
;; if there is no head-body delimiter, we search a bit manually.
(while (and (looking-at "From \\|[^ \t]+:")
(not (eobp)))
- (forward-line 1)
- (point))))
+ (forward-line 1))
+ (point)))
;; Find the Message-ID header.
(goto-char (point-min))
(if (re-search-forward "^Message-ID:[ \t]*\\(<[^>]+>\\)" nil t)
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Problem with .gnus.el
@ 1999-09-09 15:11 Bruce Lysik
0 siblings, 0 replies; 4+ messages in thread
From: Bruce Lysik @ 1999-09-09 15:11 UTC (permalink / raw)
> I guess you got a bad mail which does not contain
> "\n\n" (maybe an empty file). Anyway, I found a
> typo in nnmail-process-maildir-mail-format. Hope
> this patch solve your problem.
Applied the patch, and no luck. My Maildir directory is actually completely empty, no mail files at all.
--Bruce Lysik
(Please cc: responses to this address until my email is up and running again.)
Free web-based email, anytime, anywhere!
ZDNet Mail - http://www.zdnetmail.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Problem with .gnus.el
@ 1999-09-09 15:53 Bruce Lysik
1999-09-10 4:09 ` eldrik
0 siblings, 1 reply; 4+ messages in thread
From: Bruce Lysik @ 1999-09-09 15:53 UTC (permalink / raw)
Hrm. Actually. Are you sure about that patch?
I applied it, and then tried to byte compile it, and got an error:
1999
** variable coding-system-for-read bound but not referenced
** variable pathname-coding-system bound but not referenced
While compiling nnmail-save-active:
** variable coding-system-for-write bound but not referenced
While compiling nnmail-get-split-group:
** variable predicate bound but not referenced
** variable path bound but not referenced
While compiling toplevel forms:
!! End of stream ((#<buffer " *Compiler Input*">))
Even trying it without byte compiling it gives the same End of stream error.
--Bruce <eldrik@zdnetmail.com>
Free web-based email, anytime, anywhere!
ZDNet Mail - http://www.zdnetmail.com
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~1999-09-10 4:09 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <m3671kf2k2.fsf@quicksilver.bzl.bzl>
1999-09-09 6:13 ` Problem with .gnus.el Shenghuo ZHU
1999-09-09 15:11 Bruce Lysik
1999-09-09 15:53 Bruce Lysik
1999-09-10 4:09 ` eldrik
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).