From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: The very last macro
Date: Thu, 26 Mar 2009 15:14:18 +0100 [thread overview]
Message-ID: <fe8d59da0903260714q3e300fd8v8736f15f6f6f36fe@mail.gmail.com> (raw)
In-Reply-To: <49CB89F4.1010005@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1521 bytes --]
> why, what do you want to achieve; there are already such hooks
The original request was
sorry for the noise :
is there in mkiv a very last macro ?
I mean something like
\IamCallAtTheReallyEnd{..}
which does absolutly nothing to the pdf , and after which mkiv ends
without calls any other macro
Peter suggest to use \everylastshipout;
but this
\def\LuigisWhateverShouldHappen{\immediate\write16{BOOOM!}Something
Luigi want to do for some unknown reason.\immediate\write16{BOOOM!}}
\appendtoks\LuigisWhateverShouldHappen \to \everylastshipout
\starttext
hello
\stoptext
write
Something Luigi want to do for some unknown reason.
near the bottom of pdf (and I don't want it)
and BOOM! on log (which is a way to say that this macro was called)
Aditya suggests to put nothing to print in
\LuigisWhateverShouldHappen
and I said that it's no a robust solution .
BTW, for a specific document, this is actually a solution -- just need a bit
of test --
I'm almost sure that there is no solutions much differents from this one.
>From luatex.web , around line 22423 :
@ We don't want to leave |main_control| immediately when a |stop| command
is sensed, because it may be necessary to invoke an \.{\\output} routine
several times before things really grind to a halt. (The output routine
might even say `\.{\\gdef\\end\{...\}}', to prolong the life of the job.)
Therefore |its_all_over| is |true| only when the current page
and contribution list are empty, and when the last output was not a
``dead cycle.''
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 1766 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-03-26 14:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 9:21 luigi scarso
2009-03-25 12:01 ` Wolfgang Schuster
2009-03-25 12:35 ` luigi scarso
2009-03-25 12:41 ` Wolfgang Schuster
2009-03-25 12:52 ` luigi scarso
2009-03-25 12:57 ` Wolfgang Schuster
2009-03-25 13:11 ` luigi scarso
2009-03-25 13:19 ` Wolfgang Schuster
2009-03-25 14:00 ` luigi scarso
2009-03-25 14:44 ` Wolfgang Schuster
2009-03-25 15:01 ` luigi scarso
2009-03-25 15:25 ` Peter Rolf
2009-03-25 15:31 ` luigi scarso
2009-03-25 15:40 ` Peter Rolf
2009-03-25 15:53 ` Aditya Mahajan
2009-03-25 16:13 ` luigi scarso
2009-03-26 8:56 ` Hans Hagen
2009-03-26 9:20 ` luigi scarso
2009-03-26 9:33 ` luigi scarso
2009-03-26 9:52 ` Hans Hagen
2009-03-26 10:19 ` luigi scarso
2009-03-26 10:50 ` Hans Hagen
2009-03-26 13:08 ` luigi scarso
2009-03-26 13:58 ` Hans Hagen
2009-03-26 14:14 ` luigi scarso [this message]
2009-03-26 14:53 ` Hans Hagen
2009-03-26 15:39 ` luigi scarso
2009-03-26 17:06 ` luigi scarso
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=fe8d59da0903260714q3e300fd8v8736f15f6f6f36fe@mail.gmail.com \
--to=luigi.scarso@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).