Jean-Marc Lasgouttes wrote:
> 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.
>
You have to put it inside in some cases, for example, with \items.
Indeed, the inconsistency with which LyX treated spacing and alignment
causes weirdness with items. If you try to modify spacing in the first
item, you get this:
\begin{list}
\begin{onehalfspacing}
\item \begin{flushright} etc.
which doesn't compile. If you try to modify it in the second, then you
get this:
\begin{list}
\item Text of item
\begin{onehalfspacing}
\item \begin{flushright} etc.
and the spacing changes in the first item. I haven't explored all the
cases. But that's enough to see that there are only three options:
1. Inside in some cases, outside in others.
This may seem ugly, but it works, and in fact the code isn't ugly.
2. Inside in all cases.
This is extremely simple but doesn't work as less experienced users will
expect.
X. Outside in all cases doesn't work.
> 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.
>
3. Inside in all cases, but prohibit customization in some cases.
These cases will include moving arguments, and possibly more. I'm
inclined to think this may be best, but I'm sure we'll get complaints,
or at least questions. Some users may have used this facility, in so far
as it was available. So if we do plan to go this way, something explicit
needs to be said somewhere about packages like titlesec, at the very least.
Richard
--
==================================================================
Richard G Heck, Jr
Professor of Philosophy
Brown University
http://frege.brown.edu/heck/
==================================================================
Get my public key from http://sks.keyserver.penguin.de
Hash: 0x1DE91F1E66FFBDEC
Learn how to sign your email using Thunderbird and GnuPG at:
http://dudu.dyn.2-h.org/nist/gpg-enigmail-howto
