References: <yfiekd9oea0.fsf@triumf.ca>
            <5.1.0.14.0.20050417104145.0247e860@pop3.web.de>
            <yfiekd9oea0.fsf@triumf.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
Message-ID:  <5.1.0.14.0.20050417201522.00abd380@pop3.web.de>
Date:         Sun, 17 Apr 2005 20:54:50 +0200
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@listserv.uni-heidelberg.de>
Sender: Mailing list for the LaTeX3 project
              <LATEX-L@listserv.uni-heidelberg.de>
From: Uwe =?iso-8859-1?Q?L=FCck?= <uwe.lueck@WEB.DE>
Subject: Re: \output trick; Re: lineno.sty question
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <85hdi5ej28.fsf@gnu.org>
Precedence: list
Status: R

At 13:31 17.04.05, David Kastrup wrote:
>Donald Arseneau <asnd@TRIUMF.CA> writes:
>
> > Uwe Lück <uwe.lueck@WEB.DE> writes:
> >
> >> After a \newtoks\output,
> >
> > And, for the output routine, I think that itself is the mistake!  I
> > opine that for \output one should "bite the bullet" and do
> > \output=\expandafter{\expandafter\mymacro\the\output}
> >
>
>The problem is that you sometimes need to call the old behavior, and
>sometimes not.  In particular, if you have inserted a special penalty
>yourself, then you will deal with it yourself, not passing anything on
>and not actually calling the original output routine.

Another point: For calling the old output routine only if it is
appropriate, something like
     \edef\previous@output{\the\output}
     \output{...\previous@output...}
could be a compromise. Yet as I understand Stephan Boettcher's
(the former maintainer's) lineno.sty documentation, the purpose
seemed to have been to "come earlier" than the output routine that
multicol.sty (and longtable.sty etc.?) defines through \output{...}
-- even when it is loaded after lineno.sty. Indeed, multicol.sty would
give an error message when it would see a special penalty from
lineno. The same applies to revtex.cls + longtable.sty. And longtable
would give an error message with two of lineno's special penalties
(these admittedly were my choices, perhaps I could have avoided
the conflict). -- This could be repaired by a few additional code lines
in multicol and longtable, so the \output trick is mainly a tribute to
the littleness of hope that Standard LaTeX Packages would care
about "contrib" packages. And as soon multicol or longtable would
use the \output trick themselves, lineno could only work together
with them if loaded earlier (another bit of evidence that the \output
trick mainly is to ensure compatibility with some Standard LaTeX
packages).

-- Uwe Lueck.