Received: from webgate.proteosys.de (mail.proteosys-ag.com [62.225.9.49]) by lucy.proteosys (8.11.0/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id f7VAGf902514 for ; Fri, 31 Aug 2001 12:16:41 +0200 Received: by webgate.proteosys.de (8.11.4/8.11.0) with ESMTP id f7VAGRT21031 . for ; Fri, 31 Aug 2001 12:16:27 +0200 MIME-Version: 1.0 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f7VAGLG10686 for ; Fri, 31 Aug 2001 12:16:21 +0200 (MET DST) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C13206.06E5CA80" Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.8.56]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id MAA27577 for ; Fri, 31 Aug 2001 12:16:20 +0200 (MEST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f7VAGJG10676 for ; Fri, 31 Aug 2001 12:16:19 +0200 (MET DST) Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f7VA4Pb29540; Fri, 31 Aug 2001 12:04:25 +0200 (MET DST) Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id f7VA3bo07744; Fri, 31 Aug 2001 12:03:37 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 0506 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 31 Aug 2001 12:03:36 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id f7VA3ao07738 for ; Fri, 31 Aug 2001 12:03:36 +0200 Received: from tninet.se (lennier.tninet.se [195.100.94.105]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f7VA4Mb29526 for ; Fri, 31 Aug 2001 12:04:22 +0200 (MET DST) Received: from [195.100.226.129] (du129-226.ppp.su-anst.tninet.se [195.100.226.129]) by lennier.tninet.se (BLUETAIL Mail Robustifier 2.2.2) with ESMTP id 437175.252261.999lennier-s2 for ; Fri, 31 Aug 2001 12:04:21 +0200 In-Reply-To: <15246.43484.6491.929447@zarniwoop.kammer.uni-hannover.de> References: <15201.23735.553563.824181@istrati.zdv.uni-mainz.de> Return-Path: X-Sender: haberg@pop.matematik.su.se Content-class: urn:content-classes:message Subject: Re: Compiling from several files Date: Fri, 31 Aug 2001 10:48:35 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Hans Aberg" Sender: "Mailing list for the LaTeX3 project" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4150 This is a multi-part message in MIME format. ------_=_NextPart_001_01C13206.06E5CA80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 23:02 +0200 2001/08/30, Reinhard Kotucha wrote: > > I make use of a feature that in a project that consists of > > several files allows me to compile each LaTeX file individually, > > thus saving some compilation time while writing the > > manuscript. I think such a system might be useful for inclusion > > in LaTeX3. > >Doesn't \includeonly do what you want? The only problem I see is that >\include starts each included file on a new page, which is annoying if >this behaviour is not desired. No: If I have a main file, then \include and \includeonly controls what should be in the main document. By my system, I may have a main document which is not altered while I write on additions: Suppose one has several chapters and writes on a new chapter. Then one still wants to access the main document for reference, while only recompiling the part one is writing on. Also, if I want to fix something = in a part, then I can recompile only that part while doing the fix, and recompile the whole document only when that fix has been completed. Otherwise, I think that \include should be fixed so that it does not = start each included file on a new page. (If it can be done -- \include = probably works that way because of something with labels, or something.) Hans Aberg ------_=_NextPart_001_01C13206.06E5CA80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Compiling from several files

At 23:02 +0200 2001/08/30, Reinhard Kotucha = wrote:
>    > I make use of a feature = that in a project that consists of
>    > several files allows me = to compile each LaTeX file individually,
>    > thus saving some = compilation time while writing the
>    > manuscript. I think such = a system might be useful for inclusion
>    > in LaTeX3.
>
>Doesn't \includeonly do what you want?  The = only problem I see is that
>\include starts each included file on a new page, = which is annoying if
>this behaviour is not desired.

No: If I have a main file, then \include and = \includeonly controls what
should be in the main document. By my system, I may = have a main document
which is not altered while I write on = additions:

Suppose one has several chapters and writes on a new = chapter. Then one
still wants to access the main document for = reference, while only
recompiling the part one is writing on. Also, if I = want to fix something in
a part, then I can recompile only that part while = doing the fix, and
recompile the whole document only when that fix has = been completed.

Otherwise, I think that \include should be fixed so = that it does not start
each included file on a new page. (If it can be done = -- \include probably
works that way because of something with labels, or = something.)

  Hans Aberg

------_=_NextPart_001_01C13206.06E5CA80--