From: "Johannes Hüsing" <hannes@ruhrau.de>
Subject: Re: FLOWcharts: stray arrows in clipped regions
Date: Wed, 26 Feb 2003 22:16:39 +0100 [thread overview]
Message-ID: <20030226211639.GA686@ruhrau.de> (raw)
In-Reply-To: <001a01c2dca9$b6dc7480$0100a8c0@vademecum>
Willi Egger <w.egger@boede.nl> [Tue, Feb 25, 2003 at 09:41:30AM CET]:
> >when I process the file attached, I get arrows where they don't belong.
> >Could somebody guide me to what I am doing wrong here?
>
> I processed your chart. - There was no coloring.
> I changed the following:
>
Dear Willi,
this was very considerate of you. You encouraged me to re-try the
process while varying the installation and configuration. In an
alternative configuration it works. Thank you also for weeding out my
syntax errors.
Regards
Johannes
--
Johannes Hüsing There is something fascinating about science. One gets
hannes@ruhrau.de such wholesale returns of conjecture from such a
trifling investment of fact. Mark Twain
next prev parent reply other threads:[~2003-02-26 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 17:09 "Hüsing, Johannes"
2003-02-25 8:41 ` Willi Egger
2003-02-26 21:16 ` Johannes Hüsing [this message]
2003-03-11 23:41 ` Hans Hagen
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=20030226211639.GA686@ruhrau.de \
--to=hannes@ruhrau.de \
--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).