From: Marco Patzer <lists@homerow.info>
To: ntg-context@ntg.nl
Subject: Re: MetaPost label direction prefix
Date: Sat, 24 Aug 2013 14:31:42 +0200 [thread overview]
Message-ID: <20130824123142.GQ18239@homerow> (raw)
In-Reply-To: <5217FE32.7070909@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1506 bytes --]
On 2013–08–24 Hans Hagen wrote:
> startplaincompatibity ;
>
> label("first", origin);
>
> pair laboff.foo ; laboff.foo := (.5,-1) ;
> labxf.foo := labyf.foo := 1 ;
>
> label.foo("second", origin);
>
> stopplaincompatibity ;
Brilliant! Thanks a lot. A few things:
1) Can you replace
def useplainlabels =
let label = plain_label ;
let thelabel = plain_thelabel ;
enddef ;
with
def useplainlabels =
def label = plain_label enddef ;
def thelabel = plain_thelabel enddef ;
enddef ;
The minimal example works with your version, but the old MetaPost
code does not. The def variant works fine with both.
2) Replace
startplaincompatibity → startplaincompatibility
stopplaincompatibity → stopplaincompatibility
3) This one is truly optional and just a suggestion for a better
interface. Although it's nice to have the grouping in
start-stopplaincompatibility, it's not required here, since the
entire MetaPost instance runs in plain compatibility mode. It would
be nice to either have a non-grouped command:
def plaincompatibility =
scantokens plain_compatibity_data ;
enddef ;
Or maybe even a higher-level switch:
\defineMPinstance
[fun-with-old-MP]
[metafun]
[compatibility=plain] %% default* | plain
> As I wouldn't be surprised if there were more differences we need
> to handle.
We will find out if things break.
Marco
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-08-24 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 9:42 Marco Patzer
2013-08-23 12:48 ` Hans Hagen
2013-08-23 13:14 ` Marco Patzer
2013-08-24 0:28 ` Hans Hagen
2013-08-24 12:31 ` Marco Patzer [this message]
2013-08-25 11:49 ` 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=20130824123142.GQ18239@homerow \
--to=lists@homerow.info \
--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).