From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: The very last macro
Date: Wed, 25 Mar 2009 17:13:51 +0100 [thread overview]
Message-ID: <fe8d59da0903250913i4fe05514ia5c7e349b4ddee43@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0903251148520.27124@ybpnyubfg.ybpnyqbznva>
> You said that you wanted \LuigisWhateverShouldHappen macro to be executed,
> which in turn means that \immediate\write18 is executed, the text Something
> .... reason is written to the pdf, and the macro \imediate\write18 is
> executed.
>
> If you do not want the text to be written to the pdf, do not add it to
> \LuigisWhat... macro :-)
true, but not so robust.
\def\LuigisWhateverShouldHappen{..what ever...}
\appendtoks\LuigisWhateverShouldHappen \to \everylastshipout
\starttext
hello
\stoptext
I want be sure that
"..what ever.."
will never introduce differences with
\startext
my stuffs here
\stoptext
for *ever* "my stuff here" and for *ever* "..what ever.."
I believe that it's no possible.
Anyway
\def\LuigisWhateverShouldHappen{..what ever...}
\appendtoks\LuigisWhateverShouldHappen \to \everylastshipout
\starttext
hello
\stoptext
can be good enought .
--
luigi
___________________________________________________________________________________
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 16:13 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 [this message]
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=fe8d59da0903250913i4fe05514ia5c7e349b4ddee43@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).