From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \FlushStep eats all spaces
Date: Thu, 5 Feb 2009 21:58:42 +0100 [thread overview]
Message-ID: <8B09248B-26B9-4870-879E-5C87C95A1AF8@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0902052146020.13399@gaston.couberia.bzh>
Am 05.02.2009 um 21:49 schrieb Peter Münster:
> On Thu, 5 Feb 2009, Wolfgang Schuster wrote:
>
>> Here is a ConTeXt version of LaTeX's \g@addto@macro macro.
>>
>> \long\def\addmacro#1\to#2% better name needed
>> {\begingroup
>> \scratchtoks\expandafter{#2#1}%
>> \xdef#2{\the\scratchtoks}%
>> \endgroup}
>>
>> \addmacro\relax\to\FlushStep
>
> This seems to be just another work-around.
> Wouldn't it be better, to adjust the definition of FlushStep in
> s-pre-60.tex?
>
> Like this for example:
> \def\FlushStep{\iftrialtypesetting\else\StopStep\NextStep\StartStep
> \fi\relax}
1. Only Hans can do this.
2. This is also what happens with my macro.
3. I think it's better to use my macro than to use manual patched
\FlushStep in your file.
Wolfgang
___________________________________________________________________________________
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-02-05 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 19:03 Peter Münster
2009-02-05 19:36 ` Wolfgang Schuster
2009-02-05 20:49 ` Peter Münster
2009-02-05 20:58 ` Wolfgang Schuster [this message]
2009-02-05 21:56 ` Peter Münster
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=8B09248B-26B9-4870-879E-5C87C95A1AF8@gmail.com \
--to=schuster.wolfgang@googlemail.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).