Comment #15 on issue 3504 by [email protected]: \hspace isn't aligned properly by
\fill-line (caused by fix to issue 3330)
http://code.google.com/p/lilypond/issues/detail?id=3504
Taking a look at the LSR snippet, I see a \hspace #1 left and right, and a
\hspace #2 in the middle. Under the old behavior, none of them are
distinguishable from \null, so it does not look like "people have gotten
used to the existing behavior", more like people don't understand the
behavior and try some handwaving around it in a manner that looks sensible
to them, giving up eventually without checking that what they do has any
influence.
The proposed change would make a difference between \hspace #1 and \hspace
#2 (well, if we have just two columns, the space in the middle does not
actually matter when it is small, but the spaces left and right will do).
That means that people have a chance to know what they are doing.
Now a "restore old behavior" is certainly better than "talk indefinitely
about what should be there instead of fixing a regression". I'm working
intermittedly on the code for this one, and I think it makes sense to
deliver it together with the issue 3330 changes. So I'm not going to
invest the time to look at your patch, and I don't think that "restore the
old semantics" makes a good fit with the logic of issue 3330.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
