From: Nikolai Weibull <mailing-lists.context-users@rawuncut.elitemail.org>
Subject: Re: OT: metapost question
Date: Tue, 29 Mar 2005 00:21:14 +0200 [thread overview]
Message-ID: <20050328222114.GA5897@puritan.pcp.ath.cx> (raw)
In-Reply-To: <42486538.9050708@elvenkind.com>
* Taco Hoekwater (Mar 29, 2005 00:10):
> N := 100;
> for k=1 step 1 until N:
> beginfig(k);
> drawdot (100,100) withpen pencircle scaled k;
> endfig;
> endfor;
> end.
Wow, I never realized that. Man, I really gotta try to remember what
can be done with macro processors...,
nikolai
--
::: name: Nikolai Weibull :: aliases: pcp / lone-star / aka :::
::: born: Chicago, IL USA :: loc atm: Gothenburg, Sweden :::
::: page: minimalistic.org :: fun atm: gf,lps,ruby,lisp,war3 :::
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}
prev parent reply other threads:[~2005-03-28 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 19:54 Gerben Wierda
2005-03-28 20:12 ` Taco Hoekwater
2005-03-28 22:21 ` Nikolai Weibull [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=20050328222114.GA5897@puritan.pcp.ath.cx \
--to=mailing-lists.context-users@rawuncut.elitemail.org \
--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).