From: Dan Jacobson <jidanni@dman.ddts.net>
Cc: bug-gnu-emacs@gnu.org
Subject: FAQ: gnuplot vs. emacs' compile command
Date: Sat, 10 May 2003 13:31:43 +0800 [thread overview]
Message-ID: <871xz7jrk0.fsf@jidanni.org> (raw)
The following message is a courtesy copy of an article
that has been posted to comp.graphics.apps.gnuplot as well.
What's the big problem that
$ cat Makefile
gp:
echo "plot 'file';pause -1"|gnuplot -persist
$ make #works fine
$ emacs -eval '(compile "make")' #doesn't plot anything.
$ emacs -eval '(shell-command "make")' #works wonderfully
$ emacs -eval '(shell-command "make&")' #doesn't plot anything
Sure you'll tell me to see /usr/share/doc/gnuplot-doc/0FAQ.gz's
"7.10 Calling gnuplot in a pipe or with a gnuplot-script doesn't produce a plot!"
but even that fancy perl example doesn't cover my emacs vs. gnuplot
dilemma.
Or you will try to change the subject by offering
http://feff.phys.washington.edu/~ravel/software/gnuplot-mode/
But that doesn't answer my question of how does one run gnuplot from a
Makefile in GNU emacs' compile mode?
Don't tell me that there is no way for this to be overcome.
I will never be able to do it "because the technology Jacobson was
asking for was 5-10 years in the future." "He was essentially asking
for plugging the standard input to the standard putoff, no simple
algorithm there."
OK, one can indeed do
gp:
echo -e 1\\n2 > a
echo "plot 'a';pause $p" > b
gnuplot b
With p=-1, the compilation never finished even after the window closes.
With p=5 etc, one has to set an arbitrary time limit, however the
compilation will indeed finish.
-persist doesn't help here.
--
http://jidanni.org/ Taiwan(04)25854780
next reply other threads:[~2003-05-10 5:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 5:31 Dan Jacobson [this message]
2003-05-11 4:42 ` FAQ: gnuplot vs. emacs' compile command Dan Jacobson
2003-05-13 3:47 ` Dan Jacobson
2004-02-12 14:43 ` Kim F. Storm
2004-02-12 19:34 ` Stefan Monnier
2004-02-12 22:47 ` Kim F. Storm
2004-02-13 0:05 ` Dan Jacobson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871xz7jrk0.fsf@jidanni.org \
--to=jidanni@dman.ddts.net \
--cc=bug-gnu-emacs@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.