ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Bruce Horrocks via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Bruce Horrocks <ntg@scorecrow.com>
Subject: Re: Metapost examples seems broken
Date: Sun, 22 May 2022 12:27:39 +0100	[thread overview]
Message-ID: <B0E2DA13-6DA9-458A-979F-F419D055FF32@scorecrow.com> (raw)
In-Reply-To: <EF6DF0F3-D04F-4EF0-A335-750B6A26CF41@gmail.com>

It's archived here
<https://web.archive.org/web/20210815171931/https://tex.loria.fr/prod-graph/zoonekynd/metapost/metapost.html>

which might suffice until the author gets his certificates sorted out?


> On 22 May 2022, at 09:41, Jan-Erik Hägglöf via ntg-context <ntg-context@ntg.nl> wrote:
> 
> HI!
> 
> I have issues to access the very most useful place to get inspiration to write MetaFun code.
> 
> Google Chrome reports security issues
> 
> Maybe this could be off topic in this forum, if so, My apologize in advance. But maybe someone knows the author of this site
> 
> https://tex.loria.fr/prod-graph/zoonekynd/metapost/metapost.html
> 

—
Bruce Horrocks
Hampshire, UK

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2022-05-22 11:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-22  8:41 Jan-Erik Hägglöf via ntg-context
2022-05-22 11:27 ` Bruce Horrocks via ntg-context [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=B0E2DA13-6DA9-458A-979F-F419D055FF32@scorecrow.com \
    --to=ntg-context@ntg.nl \
    --cc=ntg@scorecrow.com \
    /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).