From: Ian Price <ianprice90@googlemail.com>
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Add ',run' and ',!'
Date: Thu, 11 Apr 2013 06:37:06 +0100 [thread overview]
Message-ID: <87a9p5eigt.fsf@Kagami.home> (raw)
In-Reply-To: <87fvyx4sqn.fsf@karetnikov.org> (Nikita Karetnikov's message of "Thu, 11 Apr 2013 08:05:20 +0400")
> So, what do you think?
This is the sort of thing that belongs in a .guile rather than in
guile IMO.
--
Ian Price -- shift-reset.com
"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"
next prev parent reply other threads:[~2013-04-11 5:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 4:05 [PATCH] Add ',run' and ',!' Nikita Karetnikov
2013-04-11 5:37 ` Ian Price [this message]
2013-04-11 23:55 ` Daniel Hartwig
2013-04-12 6:29 ` Nala Ginrut
2013-04-12 7:50 ` Daniel Hartwig
2013-04-12 9:37 ` Nala Ginrut
2013-04-12 14:38 ` Ian Price
2013-04-12 23:45 ` Nikita Karetnikov
2014-03-23 19:38 ` Andy Wingo
2014-03-23 20:03 ` Doug Evans
2013-04-12 8:46 ` Ludovic Courtès
2013-04-12 23:52 ` Nikita Karetnikov
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=87a9p5eigt.fsf@Kagami.home \
--to=ianprice90@googlemail.com \
--cc=guile-devel@gnu.org \
--cc=nikita@karetnikov.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).