From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org
Subject: Re: Bug File Format
Date: 24 Mar 2002 20:10:48 +0100 [thread overview]
Message-ID: <877ko1rdc7.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87g02pn89q.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us>
Evan Prodromou <evan@glug.org> writes:
> So, I was just thinking: although RFC822 is a just-fine data format,
> Guile has a perfectly wonderful built-in data format, namely, the
> s-expression.
Yes, I thought about this, too. But s-expression just feel unnatural
for non-nested data that is mostly straight text. I think that most
information about a bug is in the body of the 'message', and having to
write this as a Scheme string will be annoying.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-24 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-24 18:13 Bug File Format Evan Prodromou
2002-03-24 19:10 ` Marius Vollmer [this message]
2002-03-25 4:04 ` Rob Browning
2002-03-24 19:11 ` Thien-Thi Nguyen
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=877ko1rdc7.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-devel@gnu.org \
/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).