From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: Daniel Kraft <d@domob.eu>, guile-devel <guile-devel@gnu.org>
Subject: Re: Updated Guile Tutorial
Date: Sun, 20 Sep 2009 17:42:59 +0100 [thread overview]
Message-ID: <87pr9lsh2k.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <m3ljlollb7.fsf@pobox.com> (Andy Wingo's message of "Thu, 13 Aug 2009 00:27:40 +0200")
Andy Wingo <wingo@pobox.com> writes:
> 4) If you're forking to run gnuplot, why not do so from Scheme?
Coincidentally, I recently wrote this:
(define (gnuplot file-name plot-command)
(let ((pipe (open-output-pipe "gnuplot -")))
(format pipe
"\
set terminal png
set output '~a'
~a
quit
"
file-name
plot-command)
(close-pipe pipe))
(system (string-append "display " file-name)))
Example usage:
(gnuplot "table1.png"
"plot 'table1.txt' using 1:6 with lines, 4*x/log(2*x), 4*x/log(x)")
Daniel, if you feel like including this in the tutorial as an
alternative to the C code, please do so.
> Anyway, IMO, FWIW, etc. If you don't reply, I'll probably just commit
> your tutorial more-or-less as-is to the repo :)
Although the tutorial is now on the web, I still haven't done anything
as regards committing it to Git. That's not because I think we
shouldn't; it just that I haven't pondered how best to do it yet.
Neil
next prev parent reply other threads:[~2009-09-20 16:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 18:34 Updated Guile Tutorial Daniel Kraft
2009-08-12 22:27 ` Andy Wingo
2009-08-13 7:43 ` Daniel Kraft
2009-08-24 15:39 ` Daniel Kraft
2009-09-20 16:35 ` Neil Jerram
2009-09-20 20:31 ` Daniel Kraft
2010-08-19 5:41 ` Andy Wingo
2010-08-21 14:38 ` Daniel Kraft
2010-08-28 18:46 ` Andy Wingo
2009-09-20 16:42 ` Neil Jerram [this message]
2009-09-20 17:17 ` Chris Bryant
2009-09-20 21:13 ` Neil Jerram
2009-09-20 17:18 ` Chris Bryant
-- strict thread matches above, loose matches on Subject: below --
2010-09-07 13:17 Daniel Kraft
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=87pr9lsh2k.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=d@domob.eu \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).