From: Taco Hoekwater <taco.hoekwater@wkap.nl>
Subject: Re: Flowcharts
Date: Fri, 17 Sep 1999 14:59:44 +0000 (GMT) [thread overview]
Message-ID: <14306.22369.205257.363452@PC709.wkap.nl> (raw)
In-Reply-To: <37E2367B.52D8BA2C@wxs.nl>
>>>>> "Hans" == Hans Hagen <pragma@wxs.nl> writes:
Hans> Taco Hoekwater wrote:
>> Some footnotes to the almost new m-chart module and its
>> documentation. I just spend a couple of hours playing with it,
>> and noticed some peculiarities that were not completely obvious
>> from the documentation, as well as a rather nasty problem with
>> texexec:
Hans> Ok, gives us something to do the next week.
Right. From your answers, I still don't quite get what is controlling
what, but we'll see about that next week.
>> Well, once I figured out this documentation, it worked
>> perfectly.
Hans> (Even the dirty clipper?)
Never used that apart from a very short&simple test, which worked.
Hans> I will extend the module with straight lines (as suggested
Hans> by tobias) for binary charts. There will also be a proper
Hans> interface to line types, arrows, and more.
It might be possible to build a (commutative) diagrams package using
this system as well.
Hans> (Once I will implement tables this way.)
I'm doing something related to tables also, so I guess we should
compare notes soon. See you sunday,
Taco
next prev parent reply other threads:[~1999-09-17 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-17 14:11 Flowcharts Taco Hoekwater
1999-09-17 12:39 ` Flowcharts Hans Hagen
1999-09-17 14:59 ` Taco Hoekwater [this message]
2004-11-17 14:18 FLOWcharts Nikolai Weibull
2005-03-11 15:56 FLOWcharts Adam Duck
2005-03-13 21:57 ` FLOWcharts Willi Egger
2005-03-16 9:20 ` FLOWcharts h h extern
2006-09-21 9:53 FLOWcharts Adam Duck
2006-09-21 18:23 ` FLOWcharts Willi Egger
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=14306.22369.205257.363452@PC709.wkap.nl \
--to=taco.hoekwater@wkap.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).