From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: guile-devel@gnu.org
Subject: Re: [PATCH] Allow user-defined meta-commands
Date: Mon, 01 Nov 2010 04:55:31 +0100 [thread overview]
Message-ID: <87oca9aea4.fsf@newton.homeunix.net> (raw)
In-Reply-To: 877hgxx4ys.fsf@delenn.lan
On Mon, Nov 01 2010, Andreas Rottmann wrote:
> Besides allowing user-defined meta-commands, this change also refactors
> the meta-command machinery to split reading a command's arguments from
> the procedure actually implementing it, and hence allows nesting
> meta-commands. As an example of such a command, ",in" is added as a new
> meta-command.
As another example of where this patch is useful, i've got a branch of
geiser that uses new meta-commands to implement the interaction between
emacs and guile. Besides making the code cleaner and the interaction
much more robust, it has allowed us to support r6rs libraries. So here's
hope that this patch will be accepted :)
jao
prev parent reply other threads:[~2010-11-01 3:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 0:28 [PATCH] Allow user-defined meta-commands Andreas Rottmann
2010-11-01 3:55 ` Jose A. Ortega Ruiz [this message]
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=87oca9aea4.fsf@newton.homeunix.net \
--to=jao@gnu.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).