From: Ken Raeburn <raeburn@raeburn.org>
To: guile-devel <guile-devel@gnu.org>
Subject: guile and emacs, again - updated Emacs src, using non-hacked Guile, public repo
Date: Sun, 23 Aug 2009 23:54:30 -0400 [thread overview]
Message-ID: <AFA94181-8528-46E3-9DC0-4EB9726AC7E7@raeburn.org> (raw)
I've updated my code to the latest Emacs sources, and changed the
build process so that it uses an installed version of Guile instead of
a private, hacked copy. I've also got a public repository available.
My testing is mainly x11 builds using guile 1.8.7 on Mac OS X; no
Windows, no NS, but I'm planning to try building a Guile version of
Emacs.app soon; also with Guile 1.9.x (which still doesn't build
cleanly for me yet) and the BDW-GC branch.
I've got a public repository now: git://raeburn.scripts.mit.edu/guile-
emacs.git . (Note: At some point, Emacs will switch from cvs to bzr,
the git mirror will have a new, re-converted history with new commit
ids, and I'll need to rebase everything, which may cause a hiccup if
you're doing anything more than checking out and building.) The
general state of the work is described in README.GUILE at the top
level, also at http://www.mit.edu/~raeburn/README.GUILE.txt .
If you play with it a bit, please let me know -- if it works, if it
breaks, if you have patches...
I think the biggest obstacles on my side to converging with Daniel
Kraft's work are getting the string and symbol representations
converted to native Guile ones from smobs. Both objects currently
carry data in Lisp that they don't in Scheme. Anyone want to help? :-)
Ken
P.S. I was noticing recently that my first commit to the Emacs source
tree relating to this project was on 1999-08-28, just shy of ten years
ago. I'm not sure if I should celebrate or be depressed on Friday. :-)
P.P.S. It looks like work on Emacs 24 may be starting sooner rather
than later. Might be harder to get this wrapped up in time and make a
case for including it in 24...
reply other threads:[~2009-08-24 3:54 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=AFA94181-8528-46E3-9DC0-4EB9726AC7E7@raeburn.org \
--to=raeburn@raeburn.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).