From: Peter Rolf <indiego@gmx.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: The very last macro
Date: Wed, 25 Mar 2009 16:25:22 +0100 [thread overview]
Message-ID: <49CA4CE2.9050703@gmx.net> (raw)
In-Reply-To: <fe8d59da0903250801j5f29a543odaf21adc75e00389@mail.gmail.com>
luigi scarso schrieb:
> On Wed, Mar 25, 2009 at 3:44 PM, Wolfgang Schuster
> <schuster.wolfgang@googlemail.com> wrote:
>
>> Am 25.03.2009 um 15:00 schrieb luigi scarso:
>>
>>
>>> I'm not saying that this macro exists;
>>> (of course one can manipulate /bin/context (or others scripts)
>>> even rewrite \stoptext )
>>>
>> \def\LuigisWhateverShouldHappen{Something Luigi want to do for some unknown
>> reason.}
>>
>> \let\luigissavednormalend\normalend
>>
>> \def\normalend{\luigissavednormalend\LuigisWhateverShouldHappen}
>>
>
> hmm
>
> \def\LuigisWhateverShouldHappen{\immediate\write16{BOOOM!}Something
> Luigi want to do for some unknown reason.\immediate\write16{BOOOM!}}
>
> \let\luigissavednormalend\normalend
>
> \def\normalend{\luigissavednormalend\LuigisWhateverShouldHappen}
>
>
> \starttext
> hello
> \stoptext
>
>
> Ok , I don't see "Something....reason." in pdf ,but ....
> do you see BOOOM! in output or log ?
>
> I don't -- so I can't say that \LuigisWhateverShouldHappen it's the
> last macro before end run :( .
>
> Your solution looks like a macro or text after \stoptext -- we have
> already seen it -- .
>
>
>
> I start to suspect that this macro does not exists .
>
>
try
\appendtoks\LuigisWhateverShouldHappen \to \everylastshipout
Best wishes, Peter
--
"Es ist doch ein Trost,
das Geldgier manchmal blöd macht."
- Kottan in "Kottan ermittelt", Folge 9: "Die Einteilung" -
___________________________________________________________________________________
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-25 15:25 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 [this message]
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
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=49CA4CE2.9050703@gmx.net \
--to=indiego@gmx.net \
--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).