Updates:
Status: Verified
Labels: -fixed_2_15_15 fixed_2_15_13
Comment #11 on issue 1828 by philehol...@gmail.com: contextStringTuning
creates extra space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
(No comment was entered for this change.)
___
Comment #10 on issue 1828 by d...@gnu.org: contextStringTuning creates
extra space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
Well, it is more like fixed_2_15_10 and invalid_2_15_16 since
\contextStringTuning is gone by now.
If you have a commit-id, you'll
Updates:
Labels: fixed_2_15_15
Comment #9 on issue 1828 by philehol...@gmail.com: contextStringTuning
creates extra space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
Based on the date of the fix
___
bug-lilyp
Updates:
Status: Fixed
Comment #8 on issue 1828 by d...@gnu.org: contextStringTuning creates extra
space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
This went through about half a million inane commits from me and
corresponding reverts (cf. git log ly/
On Aug 29, 2011, at 7:07 PM, lilyp...@googlecode.com wrote:
>
> Comment #7 on issue 1828 by d...@gnu.org: contextStringTuning creates extra
> space after first system
> http://code.google.com/p/lilypond/issues/detail?id=1828
>
> I pushed the simple version only affecting the current context as
Comment #7 on issue 1828 by d...@gnu.org: contextStringTuning creates extra
space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
I pushed the simple version only affecting the current context as commit
2dad7be345ca1f4c04e836a56a9a66c0e340b39b
. If this leads to
Comment #6 on issue 1828 by n.putt...@gmail.com: contextStringTuning
creates extra space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
That would be the same as \set stringTunings I should think
Yeah, you're absolutely right.
_
Comment #5 on issue 1828 by d...@gnu.org: contextStringTuning creates extra
space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
So anyway, I'd just use the following instead of overengineering. If you
are in a subcontext of some staff, your tough luck. Things
Comment #4 on issue 1828 by d...@gnu.org: contextStringTuning creates extra
space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
That would be the same as \set stringTunings I should think, and the
problem is exactly that the bottom context, once the music has st
Comment #3 on issue 1828 by n.putt...@gmail.com: contextStringTuning
creates extra space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
Use the Bottom alias?
\set Bottom. stringTunings
Of course, if there's no TabStaff then you encounter the same problem.
_
Comment #2 on issue 1828 by d...@gnu.org: contextStringTuning creates extra
space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
Perhaps I am thinking too complicated. Since one gives the tuning a name,
this command would likely be used right in the start of the
Comment #1 on issue 1828 by d...@gnu.org: contextStringTuning creates extra
space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
Well, obviously one should not be setting values in non-existent contexts
since Lilypond then creates them. Ugh. I have the suspicio
Status: Accepted
Owner:
Labels: Type-Ugly
New issue 1828 by philehol...@googlemail.com: contextStringTuning creates
extra space after first system
http://code.google.com/p/lilypond/issues/detail?id=1828
Using the code below produces an extra space below the first system. Using
\set Ta
13 matches
Mail list logo
