Abdelrazak Younes ha scritto:
Bo Peng wrote:
No. The whole idea of separating chapters from a book is that I can
compile and view the chapters *quicker*. I do not want to compile the
whole book when I am working on a chapter.
Here, I actually agree with Bo. When you separate chapters/sections, you
want to work on one segment at a time, and it is quicker to
compile/preview the
current segment only, just to check real fast if that EPS image fits
well within
the column, or if the fonts are readable, etc... That said, when you
approach
the end/finalization of a document, you need to preview over and over again
the entire doc. So, in my opinion, it would be fine to have shortcuts
for both.
Probably, it wouldn't be essential to have by default shortcuts for more
than
one single preview mode, and you could have just one preview shortcut, and
a preference setting for the preview mode (DVI, PS, PDF, ...).
So, my proposal in short: shortcut for preview child and preview master, and
preference setting for the type of preview (personally, I use always the
same).
More often than not a child document won't have the same settings and
preamble as his master buffer.
I think here Abdelrazak got to the real problem. More often than not, I have
a set of settings (document class, options, preamble, macros) in the master
document that is actually needed to compile the document and of course also
some of the children documents.
The first thing I'd like to point out is that it is quite annoying to
have to repeat
the same settings to each and every child document, just to allow the
preview
of them in isolation. I would love to see a mechanism for automatic
*inheritance*
of these properties from the master, and probably with also the
possibility to
add some customizations of the children documents that are automatically
"backported" to the master.
For example, if I put a \usepackage{something} into the master preamble,
then,
when previewing a child, that line should be someway "inhereted" into the
child preamble when creating the LaTeX.
Furthermore, if I put a \usepackage{someotherthing} into a child document
preamble, then that line should be someway included also into the master
preamble when previewing the entire document (with all the necessary logics
to detect and avoid double inclusion, if needed).
Macros, theorems and environments are a pain on their own. Usually, I define
all of them into the master (I used to include a macro file with LaTeX,
but LyX
does not like that, yet). If I want to preview the child, I have to copy
the macro
definitions from the master, therefore the master will not preview
anymore due
to the double definition of macros. Also here, I'd love to see an
automatic inheritance
of macro definitions within the child documents that are included
*after* the macro
definition itself.
Bye,
T.
