From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Metapost variable problem
Date: Tue, 3 Aug 2004 15:51:19 +0200 [thread overview]
Message-ID: <20040803155119.28bf6ca2.taco@elvenkind.com> (raw)
In-Reply-To: <410F86FE.2020105@econ.muni.cz>
On Tue, 03 Aug 2004 12:37:18 +0000
Michal Kvasnicka <quasar@econ.muni.cz> wrote:
> Good afternoon.
>
> I am sorry that I bother you with this offtopic but I don't know where
> else I can ask.
There is a mailing list for metafont (and metapost). To subscribe, e-mail:
To: listserv@ens.fr
Subject: subscribe metafont Michal Kvasnicka
> Is there some simple way to do it, or have I to copy it manually like this:
> string b.type; b.type:=a.type;
> ...
direct assignment will definately not work. Some sort of automation based
on the suffix names may be possible (using forsuffixes perhaps) but writing
a dedicated macro is probably easiest.
Greetings, Taco
prev parent reply other threads:[~2004-08-03 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 12:37 Michal Kvasnicka
2004-08-03 13:51 ` Taco Hoekwater [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=20040803155119.28bf6ca2.taco@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).