Re: Issue 1298 in lilypond: minimum-Y-extent might be obsolete?
Mark wrote Wednesday, November 17, 2010 4:46 AM Comment #10 on issue 1298 by markpolesky: minimum-Y-extent might be obsolete? http://code.google.com/p/lilypond/issues/detail?id=1298 IIRC, the obsolescence only applies to VerticalAxisGroup. But VerticalAxisGroup supports the grob-interface, which provides the 'minimum-Y-extent property. Or am I misunderstanding something? The support of an interface (AFAIK) simply adds the properties specified in that interface to the list of properties that the user can set without incurring a cannot find property type-check error. The effect of setting a property depends on what the code which implements the grob chooses to do with it. This may be nothing, as in this case. Trevor ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1408 in lilypond: Enhancement: alternate ancient prall notation
Status: Accepted Owner: Labels: Type-Enhancement Priority-Low Glyph New issue 1408 by v.villenave: Enhancement: alternate ancient prall notation http://code.google.com/p/lilypond/issues/detail?id=1408 This glyph has been spotted by Swiss user Bernard Meylan on the -fr list: it seems that it was commonly used in ancient French editions to indicate some kind of prall ornaments. Unlike the scripts we use, it wasn't printed above or below the staff but on the left side of the note, always between staff lines (much like augmentation dots, except on the other side). As a result, I'm afraid a dedicated engraver would be required. Please have a look at the attached examples, taken from a Bernier cantata printed under Louis XIV. Or course, workarounds exist: http://lists.gnu.org/archive/html/lilypond-user-fr/2010-10/msg00166.html However, it would be nicer to have this natively in LilyPond (spacing-wise, etc.). Attachments: ex1 3.3 KB ex2 1.7 KB ex3 2.4 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1409 in lilypond: Enhancement: printing the repeat count when no alternatives are present
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Medium
New issue 1409 by v.villenave: Enhancement: printing the repeat count when
no alternatives are present
http://code.google.com/p/lilypond/issues/detail?id=1409
As Trevor pointed out, this feature has been requested several times
already.
http://lists.gnu.org/archive/html/lilypond-devel/2010-11/msg00405.html
It would be good to have an optional setting, off by default, which
causes the repeat count in a volta repeat to be printed above the
repeat bar line when no alternatives are present. For example,
\voltaCountOn
\repeat volta 4 { ... }
% no alternatives follow
would print x4 above the bar line closing the repeat.
James suggested another way of printing this:
I've never seen it done like that but seem to remember a normal volta
bracket on the last measure of the repeated section with '1-4' on it.
I've seen both, but the x4 is indeed commonly used in repetitive music (I
remember seeing it in Reich's Vermont Counterpoint original edition).
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1333 in lilypond: Enhancement: beamed acciaccaturas should be printed with a slash
Updates: Status: Started Owner: v.villenave Labels: Patch Comment #1 on issue 1333 by v.villenave: Enhancement: beamed acciaccaturas should be printed with a slash http://code.google.com/p/lilypond/issues/detail?id=1333 I've suggested a patch: http://codereview.appspot.com/3169041 ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1409 in lilypond: Enhancement: printing the repeat count when no alternatives are present
Comment #1 on issue 1409 by markpolesky: Enhancement: printing the repeat count when no alternatives are present http://code.google.com/p/lilypond/issues/detail?id=1409 I'm looking at the score to Reich's Music for 18 Musicians, and the x is always after the number, i.e. 4x. This is how I've always seen it elsewhere. I don't ever recall seeing x4. If x=times, it makes sense to me to play the music four times, not times four, so I'd prefer the default voltaCount to have the number first, when it's on. Also, be sure to use the UTF MULTIPLICATION SIGN × (U+00D7), not the letter x (U+0078). ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1409 in lilypond: Enhancement: printing the repeat count when no alternatives are present
Comment #2 on issue 1409 by lemzwerg: Enhancement: printing the repeat count when no alternatives are present http://code.google.com/p/lilypond/issues/detail?id=1409 A variant (as used e.g. in Wagner's `Parsifal' in the first `Verwandlung') is to write `repeat 3x' instead of `4x'. This should be written at the end of the volta block. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Tie like a slur
I've been setting some music with something like the following:
\new Staff {
\time 6/8
\clef treble
a''8 a''8 a''8 a''8 a''8 a''8
}
\new Staff {
\time 6/8
\clef bass
\voiceOne
a c' f'4. ~ b c' e'4.
}
(I've done the 2 staves because it gets the spacing on the lower one closer
to what I have).
Lily sets this as shown in the attached image - to my eyes this looks more
like a slur than a tie. Bug? Issue 139?
--
Phil Holmes
Bug Squad
attachment: TieLikeSlur.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Point-and-Click URIs not properly formed (see text at end of message)
lilypond -V -dpoint-and-click braziluke.ly (2121) warning: Relocation: is absolute: argv0=/usr/local/lilypond/usr/bin/lilypond PATH=/usr/local/lilypond/usr/bin (prepend) Setting PATH to /usr/local/lilypond/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr /bin:/bin:/usr/games:/usr/lib/java/bin:/usr/lib/java/bin:/usr/lib/qt/bin warning: Relocation: compile datadir=, new datadir=/usr/local/lilypond/usr/share/lilypond//current warning: Relocation: framework_prefix=/usr/local/lilypond/usr/bin/.. Setting INSTALLER_PREFIX to /usr/local/lilypond/usr/bin/.. Relocation file: /usr/local/lilypond/usr/bin/../etc/relocate//gs.reloc warning: no such directory: /usr/local/lilypond/usr/bin/../share/ghostscript/8.70/fonts for GS_FONTPATH warning: no such directory: /usr/local/lilypond/usr/bin/../share/gs/fonts for GS_FONTPATH GS_LIB=/usr/local/lilypond/usr/bin/../share/ghostscript/8.70/Resource (prepend) Setting GS_LIB to /usr/local/lilypond/usr/bin/../share/ghostscript/8.70/Resource GS_LIB=/usr/local/lilypond/usr/bin/../share/ghostscript/8.70/Resource/Init (prepend) Setting GS_LIB to /usr/local/lilypond/usr/bin/../share/ghostscript/8.70/Resource/Init:/usr/local/ lilypond/usr/bin/../share/ghostscript/8.70/Resource Relocation file: /usr/local/lilypond/usr/bin/../etc/relocate//pango.reloc Setting PANGO_RC_FILE to /usr/local/lilypond/usr/bin/../etc/pango/pangorc Setting PANGO_PREFIX to /usr/local/lilypond/usr/bin/../ Setting PANGO_MODULE_VERSION to 1.6.0 Relocation file: /usr/local/lilypond/usr/bin/../etc/relocate//fontconfig.reloc Setting FONTCONFIG_FILE to /usr/local/lilypond/usr/bin/../etc/fonts/fonts.conf Setting FONTCONFIG_PATH to /usr/local/lilypond/usr/bin/../etc/fonts Relocation file: /usr/local/lilypond/usr/bin/../etc/relocate//guile.reloc GUILE_LOAD_PATH=/usr/local/lilypond/usr/bin/../share/guile/1.8 (prepend) Setting GUILE_LOAD_PATH to /usr/local/lilypond/usr/bin/../share/guile/1.8 PATH=/usr/local/lilypond/usr/bin/../bin (prepend) Setting PATH to /usr/local/lilypond/usr/bin/../bin:/usr/local/lilypond/usr/bin:/usr/local/sbin: /usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/lib/java/bin:/usr/ lib/java/bin:/usr/lib/qt/bin Setting GUILE_MIN_YIELD_1 to 65 Setting GUILE_MIN_YIELD_2 to 65 Setting GUILE_MIN_YIELD_MALLOC to 65 Setting GUILE_INIT_SEGMENT_SIZE_1 to 10485760 Setting GUILE_MAX_SEGMENT_SIZE to 104857600 LILYPOND_DATADIR=/usr/share/lilypond/2.12.3 LOCALEDIR=/usr/share/locale Effective prefix: /usr/local/lilypond/usr/share/lilypond/current FONTCONFIG_FILE=/usr/local/lilypond/usr/bin/../etc/fonts/fonts.conf FONTCONFIG_PATH=/usr/local/lilypond/usr/bin/../etc/fonts GS_LIB=/usr/local/lilypond/usr/bin/../share/ghostscript/8.70/Resource/Init:/us r/local/lilypond/usr/bin/../share/ghostscript/8.70/Resource GUILE_LOAD_PATH=/usr/local/lilypond/usr/bin/../share/guile/1.8 PANGO_RC_FILE=/usr/local/lilypond/usr/bin/../etc/pango/pangorc PANGO_PREFIX=/usr/local/lilypond/usr/bin/../ PATH=/usr/local/lilypond/usr/bin/../bin:/usr/local/lilypond/usr/bin:/usr/local /sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/lib/java/bin :/usr/lib/java/bin:/usr/lib/qt/bin [] [/usr/local/lilypond/usr/share/lilypond/current/scm/lily-library.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/file-cache.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/define-event-classes.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/define-music-types.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/output-lib.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/c++.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/chord-ignatzek-names.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/chord-entry.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/chord-generic-names.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/stencil.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/markup.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/music-functions.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/part-combiner.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/autochange.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/define-music-properties.scm ] [/usr/local/lilypond/usr/share/lilypond/current/scm/auto-beam.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/chord-name.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/parser-ly-from-scheme.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/ly-syntax-constructors.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/define-context-properties.s cm] [/usr/local/lilypond/usr/share/lilypond/current/scm/translation-functions.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/script.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/midi.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/layout-beam.scm] [/usr/local/lilypond/usr/share/lilypond/current/scm/parser-clef.scm]
Re: Tie like a slur
On Wed, Nov 17, 2010 at 9:43 AM, Phil Holmes m...@philholmes.net wrote:
I've been setting some music with something like the following:
\new Staff {
\time 6/8
\clef treble
a''8 a''8 a''8 a''8 a''8 a''8
}
\new Staff {
\time 6/8
\clef bass
\voiceOne
a c' f'4. ~ b c' e'4.
}
(I've done the 2 staves because it gets the spacing on the lower one closer
to what I have).
Lily sets this as shown in the attached image - to my eyes this looks more
like a slur than a tie. Bug? Issue 139?
Looks like a bug.
It could be issue 139, or maybe issue 962.
http://code.google.com/p/lilypond/issues/detail?id=962
Thanks,
Patrick
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Point-and-Click URIs not properly formed (see text at end of message)
On Wed, Nov 17, 2010 at 9:13 AM, Mike Bagneski bagneskim...@gmail.com wrote: Using Lilypad 2.12.3, PDF files generated using command: lilypond -dpoint-and-click filename results in URIs in the form: /home/mb/lilypond/string:6:6:12 Everything looks okay, except the actual file name. In its place is input. Hmm, that's quite odd. :) Can you send me a .ly file that I can test? I can't reproduce this on my end... Thanks, Patrick ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Tie like a slur
Patrick McCarty pnor...@gmail.com wrote in message
news:aanlktimd0uobzxtpde4s0eecr4jwfoork4hp-pwwx...@mail.gmail.com...
On Wed, Nov 17, 2010 at 9:43 AM, Phil Holmes m...@philholmes.net wrote:
I've been setting some music with something like the following:
\new Staff {
\time 6/8
\clef treble
a''8 a''8 a''8 a''8 a''8 a''8
}
\new Staff {
\time 6/8
\clef bass
\voiceOne
a c' f'4. ~ b c' e'4.
}
(I've done the 2 staves because it gets the spacing on the lower one
closer
to what I have).
Lily sets this as shown in the attached image - to my eyes this looks more
like a slur than a tie. Bug? Issue 139?
Looks like a bug.
It could be issue 139, or maybe issue 962.
http://code.google.com/p/lilypond/issues/detail?id=962
Thanks,
Patrick
Sorry about the lack of above. Microsoft.
I reckon it's 139, since it's a tie outside a chord, rather than one inside
a chord. Looking at the bug list, though, it would seem that tie placement
could do with a review in the next full release. I'm tempted to push 139
to high, and add this, since it's real world and very confusing with
standard musical notation.
--
Phil Holmes
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1410 in lilypond: Rest in lower voice should be placed above notes in in upper if voices are crossed.
Status: Accepted
Owner:
Labels: Type-Other
New issue 1410 by RalphBugList: Rest in lower voice should be placed above
notes in in upper if voices are crossed.
http://code.google.com/p/lilypond/issues/detail?id=1410
\version 2.13.39
%% rests in one voice crossing other voice
{c4 c}\\
{ r8 c'' r c''}
%% Rests in mixed (rests+notes) columns don't obey Rest 'direction = #UP:
{c4 c}\\
{\override Rest #'direction = #UP r8 c'' r c''}
%% wanted output
{c4 c}\\
{\stemNeutral \override Stem #'neutral-direction = #UP r8 c'' r c''}
Related discussions and threads:
http://lists.gnu.org/archive/html/lilypond-user/2007-06/msg00350.html
http://code.google.com/p/lilypond/issues/detail?id=384
http://lists.gnu.org/archive/html/lilypond-user/2010-11/msg00014.html
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bug in rest-placement in polyphonic music
Greetings, Anders Vinjar -
I'm not top posting.
\version 2.13.39
%% rests in one voice crossing other voice
{c4 c}\\
{ r8 c'' r c''}
%% Rests in mixed (rests+notes) columns don't obey Rest 'direction = #UP:
{c4 c}\\
{\override Rest #'direction = #UP r8 c'' r c''}
%% wanted output
{c4 c}\\
{\stemNeutral \override Stem #'neutral-direction = #UP r8 c'' r c''}
Thank you for your email. This has been added as issue # 1410 :
http://code.google.com/p/lilypond/issues/detail?id=1410
Pondly,
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1411 in lilypond: Piano phrasing slur collision with lyrics
Status: Accepted
Owner:
Labels: Type-Collision
New issue 1411 by RalphBugList: Piano phrasing slur collision with lyrics
http://code.google.com/p/lilypond/issues/detail?id=1411
\version 2.12.3
%{
Phrasing slur becomes highly eccentric within a single voice when it must
move
across piano staves, and does not detect collision with lyrics on an
adjacent
staff.
Specifically related to when the slur is forced to the up direction, either
by
voicing (as per this example) or by a macro like \phrasingSlurUp
%}
\score {
\context Staff = voice \relative c'' {
\time 4/2
c4 c c c c c c c
}
\addlyrics {
foo foo foo foo foo foo foo foo
}
\new PianoStaff
\context Staff = pianoRh {
{
\change Staff = pianoLh
e''4\(
\change Staff = pianoRh
e'' c'1 c''2\)
} \\ {}
}
\new Staff = pianoLh {
s\breve
}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Piano phrasing slur collision with lyrics
On Wed, Nov 10, 2010 at 3:20 AM, Hayden Muhl haydenm...@yahoo.com wrote:
I'm not top posting
\version 2.12.3
%{
Phrasing slur becomes highly eccentric within a single voice when it must
move
across piano staves, and does not detect collision with lyrics on an
adjacent
staff.
Specifically related to when the slur is forced to the up direction, either
by
voicing (as per this example) or by a macro like \phrasingSlurUp
%}
\score {
\context Staff = voice \relative c'' {
\time 4/2
c4 c c c c c c c
}
\addlyrics {
foo foo foo foo foo foo foo foo
}
\new PianoStaff
\context Staff = pianoRh {
{
\change Staff = pianoLh
e''4\(
\change Staff = pianoRh
e'' c'1 c''2\)
} \\ {}
}
\new Staff = pianoLh {
s\breve
}
}
Greetings, Hayden Muhl -
This has been accepted as issue # 1411 :
http://code.google.com/p/lilypond/issues/detail?id=1411
Pondly,
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1290 in lilypond: Skyline compaction is going overboard sometimes
Comment #6 on issue 1290 by k-ohara5...@oco.net: Skyline compaction is
going overboard sometimes
http://code.google.com/p/lilypond/issues/detail?id=1290
Global increase of padding, either vertical (comment 2) or horizontal
(comment 3), was generally rejected at
http://lists.gnu.org/archive/html/bug-lilypond/2010-11/msg1.html.
We overlooked in that discussion, however, the fact that horizontal padding
can be applied to Systems as distinct from VerticalAxisGroup objects (see
IR 3.2.106 system-interface) :
\score {
\repeat unfold 80 { c'''-1 e'''-3 g'''-5 c' c,-1 e,-3 g,-5 c' }
\layout {
\context {
\Score
\override System #'skyline-horizontal-padding = #2
}
}
}
Padding at the System level avoids the unwanted extra space inside systems
that one gets by applying comment 3 directly.
There is regression, in that System::skyline-horizontal-padding no longer
affects the layout of systems on a page. I could not find any evidence
that anyone took advantage of the old behavior, however, so this remains a
purely hypothetical problem.
Attachments:
1209_clarify.png 34.7 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1298 in lilypond: minimum-Y-extent might be obsolete?
Issue 1298: minimum-Y-extent might be obsolete? http://code.google.com/p/lilypond/issues/detail?id=1298 This issue is now blocking issue 1299. See http://code.google.com/p/lilypond/issues/detail?id=1299 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1299 in lilypond: ly/gregorian.ly needs minimum-Y-extent updated
Updates: Blockedon: 1298 Comment #2 on issue 1299 by percival.music.ca: ly/gregorian.ly needs minimum-Y-extent updated http://code.google.com/p/lilypond/issues/detail?id=1299 This item is waiting until there's clarification of issue 1298. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1252 in lilypond: Music overflows page (one staff per system, default spacing settings, some marks)
Updates: Status: Fixed Labels: fixed_2_13_40 Comment #7 on issue 1252 by percival.music.ca: Music overflows page (one staff per system, default spacing settings, some marks) http://code.google.com/p/lilypond/issues/detail?id=1252 I cannot reproduce this with current git, so I'm marking it fixed. If somebody can produce a .ly file which demonstrates another overflow, then of course we will open a new Critical issue for that -- but with this example, at least, there's no problem any more. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1252 in lilypond: Music overflows page (one staff per system, default spacing settings, some marks)
Updates:
Status:
Labels: -fixed_2_13_40
Comment #8 on issue 1252 by joeneeman: Music overflows page (one staff per
system, default spacing settings, some marks)
http://code.google.com/p/lilypond/issues/detail?id=1252
Here's an example that overflows with current git. It doesn't overflow if
you replace RehearsalMark with TextScript.
\paper {
paper-height= 8\cm
}
\book {
\repeat unfold 3 { g'''1\mark \markup Long Text g'''1\break}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1298 in lilypond: minimum-Y-extent might be obsolete?
On Wed, 17 Nov 2010 20:39:32 -0800, bug-lilypond-requ...@gnu.org wrote: Comment #12 on issue 1298 by k-ohara5...@oco.net: minimum-Y-extent might be obsolete? http://code.google.com/p/lilypond/issues/detail?id=1298 Diff attached. Text explanation attached. (I am not set up with git to create proper patches as recognized by Reitveld.) One affected item is a Snippet. Fortunately, the modified snippet complies the same under stable and development versions, so I put it right away in the LSR. It is awaiting approval as http://lsr.dsi.unimi.it/LSR/Item?id=731 -Keith ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1299 in lilypond: ly/gregorian.ly needs minimum-Y-extent updated
On Wed, 17 Nov 2010 20:39:32 -0800, bug-lilypond-requ...@gnu.org wrote: Updates: Blockedon: 1298 Comment #2 on issue 1299 by percival.music.ca: ly/gregorian.ly needs minimum-Y-extent updated http://code.google.com/p/lilypond/issues/detail?id=1299 This item is waiting until there's clarification of issue 1298. Graham, From my point of view, Joe's last note on 1298 makes everything sufficiently clear to proceed : minimum-Y-extent is still a valid property of every grob, and VerticalAxisGroup does support the grob-interface (*1), *but* the Y-extent of VerticalAxisGroups is no longer used to determine the spacing of staves, so this particular use of minimum-Y-extent should be removed or replaced from manual/web examples. The convert-ly pattern that flags this change should be restricted to something like VerticalAxisGroup\s*#\'minimum-Y-extent. That would be a different issue, and I am about to report it in combination with a closely-related missing converty-ly rule. - Keith (*1) One might wonder why VerticalAxisGroup supports the grob-interface, being that it is not a graphical object, but that question seems outside the scope of this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
imperfect convert-ly rules
Dear Bug Squad, Convert-ly failed to convert some of my variable settings, because they are not of the form variable = #2, but rather of the form variable = 1\cm. The only problems I have seen are from the section that converts to 2.13.10. The attached text contains replacement rules for that section that have been working for me. In the same section of rules, the old use of minimum-Y-extent is flagged as obsolete. However, discussion of issue 1298 revealed that only its use with VerticalAxisGroup is obsolete, so I narrowed the rule to flag only those uses. -- Keithstr = re.sub (rpage-top-space\s*=\s*(\S+), rtop-system-spacing #'space = \1, str) str = re.sub (rbetween-system-space\s*=\s*(\S+), rbetween-system-spacing #'space = \1\nbetween-scores-system-spacing #'space = \1, str) str = re.sub (rbetween-system-padding\s*=\s*(\S+), rbetween-system-spacing #'padding = \1\nbetween-scores-system-spacing #'padding = \1, str) str = re.sub (r(after|between|before)-title-space\s*=\s*(\S+), r\1-title-spacing #'space = #\2, str) if re.search(r'VerticalAxisGroup\s*#\'minimum-Y-extent', str): stderr_write(\n) stderr_write(NOT_SMART % _(vertical spacing has been changed; minimum-Y-extent is obsolete for use in spacing staves.\n)) stderr_write(UPDATE_MANUALLY) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1385 in lilypond: Line indents confuse vertical spacing
Updates: Status: Fixed Labels: fixed_2_13_40 Comment #4 on issue 1385 by joeneeman: Line indents confuse vertical spacing http://code.google.com/p/lilypond/issues/detail?id=1385 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
