From: Neil Jerram <neil@ossau.uklinux.net>
Cc: rlb@defaultvalue.org, guile-devel@gnu.org
Subject: Re: Handling BUGS.
Date: 22 Mar 2002 09:14:53 +0000 [thread overview]
Message-ID: <m38z8lx8tu.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <E16oIdr-00027n-00@giblet>
>>>>> "thi" == Thien-Thi Nguyen <ttn@giblet.glug.org> writes:
thi> how about promote devel/ out of guile-core/ entirely? it is
thi> generally not related to any specific branch. bugs
thi> housekeeping is part of the development effort, after all...
That sounds good to me. It makes sense to me to track both bugs and
future enhancements in a similar kind of way.
(BTW, anyone looking for a data mining job? There's a goldmine of
useful discussion on future enhancements (which may also be
simplifications, of course) in the mailing list archive.)
thi> might as well specify a known format, how about rfc822? it's
thi> time to see how well the elisp translation machinery holds up
thi> to rfc822.el (moderately hairy load IMHO). if not, someone
thi> will check in rfc822.scm soon i'm sure.
Now you're playing dirty!
Handling rfc822.el will require a basic buffer implementation:
forward-char, insert, buffer-substring etc. etc. But surely that's a
more interesting task for someone than translating rfc822.el as a
whole to rfc822.scm.
(To make it really interesting/useful, do this by preprocessing the
relevant source files from the Emacs distribution. (Damn, I'm quite
tempted myself now.))
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-22 9:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 17:12 Handling BUGS Rob Browning
2002-03-21 23:09 ` Neil Jerram
2002-03-22 0:54 ` Rob Browning
2002-03-22 9:03 ` Neil Jerram
2002-03-22 6:35 ` Thien-Thi Nguyen
2002-03-22 9:14 ` Neil Jerram [this message]
2002-03-22 14:25 ` Rob Browning
2002-03-22 19:32 ` Thien-Thi Nguyen
2002-03-22 17:40 ` Evan Prodromou
2002-03-22 19:13 ` Thien-Thi Nguyen
2002-03-22 19:40 ` Evan Prodromou
2002-03-22 20:08 ` Thien-Thi Nguyen
2002-03-22 20:34 ` Evan Prodromou
2002-03-22 21:41 ` Thien-Thi Nguyen
2002-03-22 22:33 ` Rob Browning
2002-03-23 0:53 ` Thien-Thi Nguyen
2002-03-23 12:14 ` Marius Vollmer
2002-03-23 14:12 ` Rob Browning
2002-03-23 14:59 ` Rob Browning
2002-03-24 19:14 ` Marius Vollmer
2002-03-23 21:43 ` Thien-Thi Nguyen
2002-03-24 13:37 ` Marius Vollmer
2002-03-24 19:31 ` Thien-Thi Nguyen
2002-03-24 20:40 ` Marius Vollmer
2002-03-24 21:13 ` Rob Browning
2002-03-24 22:00 ` Marius Vollmer
2002-03-25 3:57 ` Rob Browning
2002-03-25 8:32 ` Thien-Thi Nguyen
2002-03-25 21:05 ` Marius Vollmer
2002-03-25 21:34 ` Thien-Thi Nguyen
2002-03-25 22:31 ` Marius Vollmer
2002-03-25 23:22 ` Thien-Thi Nguyen
2002-03-25 23:39 ` Thien-Thi Nguyen
2002-03-22 20:34 ` Thien-Thi Nguyen
2002-03-22 22:31 ` Rob Browning
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=m38z8lx8tu.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=rlb@defaultvalue.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).