Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.6713); Mon, 22 Mar 2004 00:57:20 +0100 Received: by mail.proteosys.com (8.12.10/8.12.2) with ESMTP id i2LNvA1s006193 for ; Mon, 22 Mar 2004 00:57:18 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.119.176]) by relay2.uni-heidelberg.de (8.12.10/8.12.10) with ESMTP id i2LNpQSe008314; Mon, 22 Mar 2004 00:51:26 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C40FA0.3F09B000" Received: from listserv (listserv.uni-heidelberg.de [129.206.119.176]) by listserv.uni-heidelberg.de (8.12.7/8.12.7/SuSE Linux 0.6) with ESMTP id i2L77qZ0029452; Mon, 22 Mar 2004 00:50:49 +0100 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8e) with spool id 53914 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 22 Mar 2004 00:50:49 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.12.7/8.12.7/SuSE Linux 0.6) with ESMTP id i2LNemN6003945 for ; Mon, 22 Mar 2004 00:40:48 +0100 Received: from fencepost.gnu.org (fencepost.gnu.org [199.232.76.164]) by relay.uni-heidelberg.de (8.12.10/8.12.10) with ESMTP id i2LNfIiv023191 for ; Mon, 22 Mar 2004 00:41:18 +0100 (MET) Received: from fencepost.gnu.org ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.24) id 1B5CV2-0002n5-Ot for LATEX-L@listserv.uni-heidelberg.de; Sun, 21 Mar 2004 18:37:01 -0500 In-Reply-To: <200403212228.36289.tim@birdsnest.maths.tcd.ie> Lines: 35 References: <200403212228.36289.tim@birdsnest.maths.tcd.ie> Return-Path: X-OriginalArrivalTime: 21 Mar 2004 23:57:20.0560 (UTC) FILETIME=[3F5F2300:01C40FA0] User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: 0 () Content-class: urn:content-classes:message Subject: Re: A proposal for \includeonly... Date: Mon, 22 Mar 2004 00:41:10 +0100 Message-ID: A X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: A proposal for \includeonly... Thread-Index: AcQPoD99wtmJxHLoSDGTsQcacjtTQg== From: "David Kastrup" Sender: "Mailing list for the LaTeX3 project" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4766 This is a multi-part message in MIME format. ------_=_NextPart_001_01C40FA0.3F09B000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Timothy Murphy writes: > On Sunday 21 March 2004 18:26, David Kastrup wrote: > > > That would mean that I could start an included file chapter2.tex > > with > > > > \includeonly[mainfile]{chapter2} > > > > and compilation of chapter2.tex would then instead compile mainfile > > with \includeonly{chapter2} active. > > > > Something like that. This would make working with \includeonly a = lot > > more convenient. > > Doesn't askinclude.sty do something like this? > Then you can just say "latex mainfile" > and specify chapter 2 once - > it remembers your choice on subsequent occasions, > unless you change it. That's rather inconvenient to use in a typical TeX shell, whereas running a file through the shell (or on the command line) is comparatively easy. Of course, as proposed this has to be in the core: an included file can't request loading a package in case it is actually only included instead of being run as the main file. > But I'm sure you know all that - you probably wrote asking.sty . Pffft. I wrote almost nothing. I am just good at bragging. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum ------_=_NextPart_001_01C40FA0.3F09B000 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: A proposal for \includeonly...

Timothy Murphy <tim@BIRDSNEST.MATHS.TCD.IE> = writes:

> On Sunday 21 March 2004 18:26, David Kastrup = wrote:
>
> > That would mean that I could start an = included file chapter2.tex
> > with
> >
> >   = \includeonly[mainfile]{chapter2}
> >
> > and compilation of chapter2.tex would then = instead compile mainfile
> > with \includeonly{chapter2} active.
> >
> > Something like that.  This would make = working with \includeonly a lot
> > more convenient.
>
> Doesn't askinclude.sty do something like = this?
> Then you can just say "latex = mainfile"
> and specify chapter 2 once -
> it remembers your choice on subsequent = occasions,
> unless you change it.

That's rather inconvenient to use in a typical TeX = shell, whereas
running a file through the shell (or on the command = line) is
comparatively easy.

Of course, as proposed this has to be in the core: an = included file
can't request loading a package in case it is = actually only included
instead of being run as the main file.

> But I'm sure you know all that - you probably = wrote asking.sty .

Pffft.  I wrote almost nothing.  I am just = good at bragging.

--
David Kastrup, Kriemhildstr. 15, 44793 Bochum

------_=_NextPart_001_01C40FA0.3F09B000--