Mojca Miklavec wrote:
On 4/3/06, Taco Hoekwater wrote:
But, since you are not really supposed to compile the project
file in the first place
Why not / What's [so] wrong with that?
It is like putting the entire life's work of an author into
a single bound volume.
I (mis)use that
Mojca Miklavec wrote:
On 4/3/06, Taco Hoekwater wrote:
But, since you are not really supposed to compile the project
file in the first place
Why not / What's [so] wrong with that?
a project mentions products and environments
you run a product and/or components (of products);
On 4/3/06, Taco Hoekwater wrote:
But, since you are not really supposed to compile the project
file in the first place
Why not / What's [so] wrong with that?
I (mis)use that mechanism for compiling either separate sections
versus the whole document. I miss the functionality of
On Mon, 3 Apr 2006, Taco Hoekwater wrote:
Aditya Mahajan wrote:
Each component starts with \title which does a page break. There are
no local setups in any component. I expected that each component will
be typed out in the same manner, whether I compile the a component,
a product or the
Aditya Mahajan wrote:
Each component starts with \title which does a page break. There are
no local setups in any component. I expected that each component will
be typed out in the same manner, whether I compile the a component,
a product or the entire project.
The fact that the page
Aditya Mahajan wrote:
Hi,
I have run into a strange kind of a problem and I am not sure on how
to debug to figure out what is going wrong. Maybe someone with more
experience with context can help me here.
I have the following document structure
project: main.tex
