unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Subject: scripts/read-rfc822 unbound "lines"
Date: Wed, 07 Jul 2004 09:38:33 +1000	[thread overview]
Message-ID: <878ydwk8p2.fsf@zip.com.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 367 bytes --]

read-rfc822 doesn't seem to like messages with header continuations,
it errors out with "lines" unbound.

A wild guess at what it might be meant to be,

        * scripts/read-rfc822 (parse-message): Correction to header
        continuation, loop with read-line not cdr lines.

I wasn't actually trying to use this, it just showed up when I ran
lint over the code.


[-- Attachment #2: read-rfc822.lines.diff --]
[-- Type: text/plain, Size: 833 bytes --]

--- read-rfc822.~1.1.~	2002-05-13 20:12:14.000000000 +1000
+++ read-rfc822	2004-07-05 17:19:25.000000000 +1000
@@ -5,7 +5,7 @@
 !#
 ;;; read-rfc822 --- Validate RFC822 file by displaying it to stdout
 
-;; 	Copyright (C) 2002 Free Software Foundation, Inc.
+;; 	Copyright (C) 2002, 2004 Free Software Foundation, Inc.
 ;;
 ;; This program is free software; you can redistribute it and/or
 ;; modify it under the terms of the GNU General Public License as
@@ -97,7 +97,7 @@
              (set! body-lines (drain-message port)))
             ((regexp-exec header-cont-rx line)
              => (lambda (m)
-                  (loop (cdr lines)
+                  (loop (read-line port)
                         (cons (match:suffix m) current-header))))
             (else
              (and current-header (add-header! current-header))

[-- Attachment #3: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel

                 reply	other threads:[~2004-07-06 23:38 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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878ydwk8p2.fsf@zip.com.au \
    --to=user42@zip.com.au \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).