fyi, glug.org/snap BUGS "details" bye bye for now

[Thien-Thi Nguyen]

folks,

bugs are now kept in the workbook/bugs/ database.  rather than continue
to publish out of date info, that page now just refers to the raw db
(which is human readable, btw).  the fancy display will return in full
glory at some point in the future (when "render-bugs" is written).

if you're interested in working on this, let me know and i'll modify the
TODO item "write render-bugs, add to mscripts or guile-tools" to record
your intent.  below is commentary from a simple rfc822 parser in the
process of being added to guile, that you can use for front-end.  feel
free to suggest improvements in the interface to accomodate render-bugs.

if you don't want to worry about paperwork for guile, that's ok.  i can
use your program on glug.org in any case.  however, i would be very
pleased to include it as part of guile if that can be arranged.

thi


_______________________________________________________
;; module name: (scripts read-rfc822)
;;
;; This module exports the proc `read-rfc822':
;;   (read-rfc822 mailmsg)
;;
;; Read MAILMSG, return a query proc.
;; MAILMSG may be a list of lines (w/o terminating newline) or a port.
;; The query proc takes a symbol COMP, and returns the message component
;; COMP.  Supported values for COMP are:
;;   from    -- first whitespace-delimited token after "^From " on first line
;;   headers -- the headers as an alist (keys are strings), order maintained
;;   body    -- rest of the mail message
;; Any other query results in a "bad component" error.