From: Rob Browning <rlb@defaultvalue.org>
Cc: Evan Prodromou <evan@glug.org>, guile-devel@gnu.org
Subject: Re: Bug File Format
Date: Sun, 24 Mar 2002 22:04:04 -0600 [thread overview]
Message-ID: <87pu1t2szv.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <877ko1rdc7.fsf@zagadka.ping.de> (Marius Vollmer's message of "24 Mar 2002 20:10:48 +0100")
Marius Vollmer <mvo@zagadka.ping.de> writes:
> 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.
I agree -- this seems like a good idea at first glance, but unless we
have some good wrapping algorithms, and some fancy emacs macros,
typing the main body information associated with a bug seems like it
might be a PITA. It'll also be hard to easily append emails/patches,
etc., since they'd all need to be properly quoted. I suppose we might
be able to get by with sexps for the header fields, but I don't feel
strongly about this either way.
However, I do feel like if we find ourselves trying to define anything
very complex at all wrt quoting/escaping, etc., then we need to
revisit this issue more seriously. As you point out, as far as
parsers go, "We've already got one."
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-25 4:04 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
2002-03-25 4:04 ` Rob Browning [this message]
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=87pu1t2szv.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=evan@glug.org \
--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).