From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: everybeforeoutput vs everyafteroutput
Date: Fri, 10 Mar 2017 17:36:10 +0100 [thread overview]
Message-ID: <3a1e7bc1-5e56-0abe-c3fd-a37faec031be@wxs.nl> (raw)
In-Reply-To: <ECF47E09-2E47-48C6-B712-989EAEA42841@arch.ethz.ch>
On 3/10/2017 10:07 AM, Michael Eidenbenz wrote:
> hello,
>
> i try to understand the difference of everybeforeoutput and everafteroutput to inject some pages. it seems as there is no difference.
> \the\everybeforeoutput is placed after the output of the page:
>
> \newtoks\Before
> \appendtoks
> \the\Before
> \global\Before\emptytoks
> \to\everybeforeoutput
>
> \newtoks\After
> \appendtoks
> \the\After
> \global\After\emptytoks
> \to\everyafteroutput
>
> \starttext
> \input{knuth}\par
> \appendtoks{before}\to\Before
> \appendtoks{after}\to\After
> \stoptext
>
>
> this code in page-otr.mkvi seems to put it before the content:
>
> \def\page_otf_set_engine_output_routine#content%
> {\global\output
> {\inotrtrue
> \the\everybeforeoutput
> #content\relax
> \the\everyafteroutput}}
>
> can this be fixed?
there is nothing wrong .. you feed something in the output routine there
you can try to use one of the other \before\after ones but be aware of
possible interferences with tex's state, hold content etc ...
\startpostponing ... might do what you want
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-03-10 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 9:07 Michael Eidenbenz
2017-03-10 16:36 ` Hans Hagen [this message]
2017-03-11 21:55 ` Michael Eidenbenz
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=3a1e7bc1-5e56-0abe-c3fd-a37faec031be@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).