From: Nala Ginrut <nalaginrut@gmail.com>
To: KAction@gnu.org
Cc: guile-devel@gnu.org
Subject: Re: Doctest as guild script
Date: Fri, 27 Sep 2013 18:06:06 +0800 [thread overview]
Message-ID: <1380276366.2898.31.camel@Renee-desktop.suse> (raw)
In-Reply-To: <1380274534-5187-1-git-send-email-KAction@gnu.org>
On Fri, 2013-09-27 at 13:35 +0400, KAction@gnu.org wrote:
> Here is patch (I wrote about it two weeks ago or so).
>
> During moving to guild I found one more limitation --- if called
> in REPL, (doctest "(foo)") do not restore previous state of
> interpreter. I am going to improve it and continuation master's
> advice is welcome.
>
> Another issue is license. I did not signed paper about Guile
> (unfortunately, it is impossible to sign paper for all GNU
> project at once). Is it critical for such non-essensial part of
> Guile?
>
IIRC it's trivial for small fix
> Best regards
>
>
next prev parent reply other threads:[~2013-09-27 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 9:35 Doctest as guild script KAction
2013-09-27 10:06 ` Nala Ginrut [this message]
2013-09-27 18:01 ` Mark H Weaver
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=1380276366.2898.31.camel@Renee-desktop.suse \
--to=nalaginrut@gmail.com \
--cc=KAction@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).