From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: [PATCH] Single stepping through code from Emacs
Date: Thu, 17 Jul 2008 22:46:35 +0100 [thread overview]
Message-ID: <49dd78620807171446l5eb5371fobc4586a099dd9c61@mail.gmail.com> (raw)
In-Reply-To: <873amb379c.fsf@gnu.org>
2008/7/15 Ludovic Courtès <ludo@gnu.org>:
> Hi,
>
> "Neil Jerram" <neiljerram@googlemail.com> writes:
>
>> Here is a minor enhancement to Guile's Emacs support. I'll commit in
>> a few days; let me know if you have any comments before that.
>
> Looks very nice!
>
> Thanks,
> Ludo'.
Thanks, that's in now, and with ChangeLogs :-)
Neil
prev parent reply other threads:[~2008-07-17 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-12 19:15 [PATCH] Single stepping through code from Emacs Neil Jerram
2008-07-15 8:02 ` Ludovic Courtès
2008-07-15 15:19 ` LTDL path problems guile 1.8.5 Roland Orre
2008-07-15 15:54 ` Ludovic Courtès
2008-07-17 21:46 ` Neil Jerram [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=49dd78620807171446l5eb5371fobc4586a099dd9c61@mail.gmail.com \
--to=neiljerram@googlemail.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=ludo@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).