ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to prevent empty page after MPpage?
Date: Mon, 13 Jul 2009 10:56:47 +0200	[thread overview]
Message-ID: <6faad9f00907130156i10bc2000qb76c4fbab3a6af50@mail.gmail.com> (raw)
In-Reply-To: <4A5AE72E.5060900@wxs.nl>

On Mon, Jul 13, 2009 at 09:50, Hans Hagen wrote:
> Mojca Miklavec wrote:
>
>>> \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

The macro handles both MKII and MKIV and I had problem in MKII. Not
all restrictions are gone now (I still get "memory limit exceeded" in
MKIV) and even if MP handles long lines now ... I don't want to risk
since the code is already there anyway.

>> 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?

That macro has been written back in 2006 I guess. I didn't try to
remove newlines, but the output of gnuplot could be as long as 1
million characters or more, so it's better to keep the lines splitted.
Not that those million characters would make sense: usually TeX
complains first about memory limit exceeded, but soon after that (even
in MKIV) metapost starts complaining. The TikZ terminal almost works
and that one manages to digest the contents (it just takes forever
before it's done).

(The point is not me trying to remove the limitation locally as any
other user will stumble upon the same limitation. I'll keep the
newlines there.)

To Vafa: I meant \obeyMPlines, not \obeylines, and that one behaves a
bit different.

Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2009-07-13  8:56 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
2009-07-13  8:56           ` Mojca Miklavec [this message]
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=6faad9f00907130156i10bc2000qb76c4fbab3a6af50@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.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).