From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to prevent empty page after MPpage?
Date: Mon, 13 Jul 2009 09:50:06 +0200 [thread overview]
Message-ID: <4A5AE72E.5060900@wxs.nl> (raw)
In-Reply-To: <6faad9f00907121419m1e9f0acw3673939c70a41977@mail.gmail.com>
Mojca Miklavec wrote:
> On Sun, Jul 12, 2009 at 23:02, Wolfgang Schuster wrote:
>> Am 12.07.2009 um 22:49 schrieb Mojca Miklavec:
>>
>>> This is a complete minimal example (no need for any external package).
>>> It seems that \obeyMPlines or something related introduces a space
>>> somewhere, and that generates an empty page.
>> Why don't you use grouping then?
ah .. wolfgang was ahead of me -)
> I guess because I don't understand what's going on in the first place :)
>
>> \def\startGNUPLOTpage
>> {\begingroup\obeyMPlines\dostartGNUPLOTpage}
>>
>> \long\def\dostartGNUPLOTpage#1\stopGNUPLOTpage
>> {\endgroup\startMPpage#1\stopMPpage}
>
> Thanks a lot!!! The magic apparently works. I don't understand what
> exactly the "obeylines" macro does (it seems that it just makes sure
> that none of line endings get lost, not even inside definition
> itself).
it is not relevant here i think; there was a time when mp could not
handle long lines so mkii has the option to split the source into lines
(after a ;) which then makes mp happy
that restriction is no longer there
> I had enough problems convincing the macro itself to work (metapost
> was complaining about too long lines otherwise), but I would
> definitely not come to the idea of ending the group even before the
> real macro starts :)
oh? how old is your mp? can't you set the buffer to 200K in texmf.cnf?
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-07-13 7:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-12 16:02 Mojca Miklavec
2009-07-12 20:45 ` Hans Hagen
2009-07-12 20:49 ` Mojca Miklavec
2009-07-12 21:02 ` Wolfgang Schuster
2009-07-12 21:19 ` Mojca Miklavec
2009-07-13 6:18 ` Vafa Khalighi
2009-07-13 8:02 ` Hans Hagen
2009-07-13 7:50 ` Hans Hagen [this message]
2009-07-13 8:56 ` Mojca Miklavec
2009-07-13 12:40 ` Hans Hagen
2009-07-13 7:47 ` 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=4A5AE72E.5060900@wxs.nl \
--to=pragma@wxs.nl \
--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).