From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: positiongraphics
Date: Wed, 12 Jul 2006 10:21:07 +0200 [thread overview]
Message-ID: <44B4B0F3.2030801@elvenkind.com> (raw)
In-Reply-To: <C71B58A1-596A-4C85-9DAB-37655686EC44@science.uva.nl>
Hans van der Meer wrote:
> I send the offending mpgraph.mp file. It has ;'s all over. There are so
> many ;;'s and even some ;;;'s that I am tempted to think that one of
> the translation scripts is the culprit, adding a ; per newline maybe? I
> am sorry not having taken a look into the ruby scripts, but my ruby
> knowledge is nihil.
The tex input file would be more useful. The mpgraph file is
autogenerated from that, after all.
Taco
next prev parent reply other threads:[~2006-07-12 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 18:49 positiongraphics Hans van der Meer
2006-07-08 21:16 ` positiongraphics Hans van der Meer
2006-07-11 13:13 ` positiongraphics Taco Hoekwater
2006-07-11 15:08 ` positiongraphics Hans Hagen
2006-07-11 19:43 ` positiongraphics Hans van der Meer
2006-07-12 8:21 ` Taco Hoekwater [this message]
2006-07-12 19:52 ` positiongraphics Hans van der Meer
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=44B4B0F3.2030801@elvenkind.com \
--to=taco@elvenkind.com \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).