>>>>> "Richard" == Richard Heck <[EMAIL PROTECTED]> writes:
Richard> One question is how spacing and alignment should be handled
Richard> in commands that have moving arguments. The existing code is
Richard> inconsistent: \begin{onehalfspacing}
Richard> \section{\protect\begin{flushright}Section
Richard> Name\protect\end{flushright}} \end{onehalfspacing} So the
Richard> alignment goes with the argument, the spacing outside it. My
Richard> view is that both should go outside, lest the user get an odd
Richard> surprise in the table of contents and page headings.
Putting the outside seems reasonable. But I do not see why you should
do something different for commands with moving arguments and without.
I am opposed to this approach.
Richard> (Another option would be simply to prohibit this kind of
Richard> thing altogether. As Andre' said, it's really a misuse of
Richard> LaTeX.)
It would be a good idea, probably.
Richard> Other question: Part of what causes a problem in tables is
Richard> the occurrence of \par at the end of every
Richard> \begin{flushright}, etc, environment that LyX outputs. (I've
Richard> removed it from the above.) Is this really necessary? Surely
Richard> it's not always necessary, and it's the cause of a lot of
Richard> problems here. The current patch just removes it, but it's
Richard> trivial to put it back, and it wouldn't be too much harder if
Richard> we wanted it sometimes but not other times. I just need to
Richard> know when we need it and when we don't.
This is actually the proverbial can of worm. Juergen, you are probably
the one who knows best about this (alignment and tables).
JMarc
