From: "John R. Culleton" <john@wexfordpress.com>
Cc: Willi Egger <w.egger@boede.nl>
Subject: Re: Chart module problem.
Date: Sat, 2 Jul 2005 18:06:27 +0000 [thread overview]
Message-ID: <200507021806.27192.john@wexfordpress.com> (raw)
In-Reply-To: <42C6F6FA.5040502@boede.nl>
On Saturday 02 July 2005 08:20 pm, Willi Egger wrote:
> Hi John,
>
> Here your code compiles as soon as you change \stopflowchart into
> \stopFLOWchart!
>
> Willi
See, I knew it was something simple staring me in the face. Or
perhaps I am the thing that is simple. Anyhow, back to the
(virtual) drawing board. I hope a have a more challenging
question later.
Thanks very much for a prompt response.
--
John Culleton
Books with answers to marketing and publishing questions:
http://wexfordpress.com/tex/shortlist.pdf
Book coaches, consultants and packagers:
http://wexfordpress.com/tex/packagers.pdf
prev parent reply other threads:[~2005-07-02 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-02 14:33 John R. Culleton
2005-07-02 20:20 ` Willi Egger
2005-07-02 18:06 ` John R. Culleton [this message]
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=200507021806.27192.john@wexfordpress.com \
--to=john@wexfordpress.com \
--cc=ntg-context@ntg.nl \
--cc=w.egger@boede.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).