From: Wilfred Hughes <me@wilfred.me.uk>
To: guile-devel <guile-devel@gnu.org>
Subject: Status of elisp support in Guile
Date: Thu, 6 Oct 2016 22:42:17 -0400 [thread overview]
Message-ID: <CAFXAjY7CkuLs8bteLP4zs8ix3GXtyRGO2yULCdsY_XQ+jKrFsA@mail.gmail.com> (raw)
I've noticed that NEWS in Guile trunk says:
** Complete Emacs-compatible Elisp implementation
However, I can see that there are 36 commits on the wip-elisp branch
that aren't in master. For example, defsubst support[1] seems only to
be on wip-elisp branch. It's still the case the guile-emacs docs[2]
recommend using the wip-elisp branch.
I can merge master into wip-elisp only one trivial conflict[3]. Can
anyone shed any light on the work outstanding here, and the process to
land these patches? Relatedly, what's the process for getting commit
access to Guile?
Wilfred
1: defsubst declaration:
http://git.savannah.gnu.org/cgit/guile.git/commit/?h=wip-elisp&id=69b80315b53d237c048afaa9692fa96f1c0a3536
and use: http://git.savannah.gnu.org/cgit/guile.git/commit/?h=wip-elisp&id=9f316dd7533d2532aabbce8ee2a2c9c326e7fb91
2: guile-emacs docs: https://www.emacswiki.org/emacs/GuileEmacs
particularly the build instructions (which I've recently refactored):
https://www.emacswiki.org/emacs/GuileEmacsBuild
3: conflict: 'check symbols constants uninterned'
http://git.savannah.gnu.org/cgit/guile.git/commit/?h=wip-elisp&id=175b64aed21df66061e00d2a7063fc6533f08d66
seems to have been independently fixed in master 'Don't serialize
uninterned symbols'
http://git.savannah.gnu.org/cgit/guile.git/commit/?id=1d72d469517ca858736bfc227d8382bfb1d84b21
next reply other threads:[~2016-10-07 2:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 2:42 Wilfred Hughes [this message]
2016-10-10 23:35 ` Status of elisp support in Guile Christopher Allan Webber
2016-10-15 2:36 ` Wilfred Hughes
2016-10-17 14:53 ` Christopher Allan Webber
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=CAFXAjY7CkuLs8bteLP4zs8ix3GXtyRGO2yULCdsY_XQ+jKrFsA@mail.gmail.com \
--to=me@wilfred.me.uk \
--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).