inconsistent treatment of vertical spacing variables?
why do we have to specify a list for the VerticalAxisGroup.staff-staff-spacing while e.g. for the StaffGrouper.staff-staff-spacing you can define single items and also all the other vertical spacers like default-staff-staff-spacing, nonstaff-relatedstaff-spacing, nonstaff-unrelatedstaff-spacing etc. accept single values? Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/inconsistent-treatment-of-vertical-spacing-variables-tp148551.html Sent from the Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Invitation to connect on LinkedIn
LinkedIn I'd like to add you to my professional network on LinkedIn. - Ralph Ralph Palmer Retired at Home Springfield, Massachusetts Area Confirm that you know Ralph Palmer: https://www.linkedin.com/e/-ei0hyc-hjr07h7z-6h/isd/15380797173/Zf2qWks4/?hs=falsetok=36ds9kuL0tKBQ1 -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/-ei0hyc-hjr07h7z-6h/v9WAHNRFrvuTdl9uIXopzIrnONGp94RV/goo/bug-lilypond%40gnu%2Eorg/20061/I5120570912_1/?hs=falsetok=2oaLMNe8wtKBQ1 (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: inconsistent treatment of vertical spacing variables?
Eluze elu...@gmail.com writes: why do we have to specify a list for the VerticalAxisGroup.staff-staff-spacing while e.g. for the StaffGrouper.staff-staff-spacing you can define single items and also all the other vertical spacers like default-staff-staff-spacing, nonstaff-relatedstaff-spacing, nonstaff-unrelatedstaff-spacing etc. accept single values? Have an example? -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: inconsistent treatment of vertical spacing variables?
David Kastrup wrote
Eluze lt;
eluzew@
gt; writes:
why do we have to specify a list for the
VerticalAxisGroup.staff-staff-spacing while e.g. for the
StaffGrouper.staff-staff-spacing you can define single items and also all
the other vertical spacers like default-staff-staff-spacing,
nonstaff-relatedstaff-spacing, nonstaff-unrelatedstaff-spacing etc.
accept
single values?
Have an example?
here:
\score {
\new PianoStaff \with {
\override VerticalAxisGroup.staff-staff-spacing.basic-distance = #35
}
\new Staff { c''1 c'' c''2 c'' }
\new Staff { \clef bass e1 f e2 d }
}
and here is part of the log:
GNU LilyPond 2.17.23
…
warning: type check for `staff-staff-spacing' failed; value
`((basic-distance . 35) . #unpure-pure-container #lt;primitive-procedure
ly:axis-group-interface::calc
:
:
taff-staff-spacing #primitive-procedure
ly:axis-group-interface::calc-pure-staff-staff-spacing )' must be of type
`list'
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/inconsistent-treatment-of-vertical-spacing-variables-tp148551p148559.html
Sent from the Bugs mailing list archive at Nabble.com.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
vim syntax highlighting on Windows
Hi all, I'm temporarily on a windows machine, and a I'm trying to get the syntax highlighting to work with vim. I followed the instructions in the docs here: http://lilypond.org/doc/v2.17/Documentation/usage/text-editor-support.html#vim-mode When I opened an .ly file in vim, I got this error: Error detected while processing C:\Program Files\LilyPond\usr\share\lilypond\current\vim\syntax\lilypond.vim: line 54: E108: No such variable: b:current_syntax I changed the offending line (unlet b:current_syntax) to: if exists(b:current_syntax) unlet b:current_syntax endif and the error message went away. Is that a bug? Also, I cannot get scheme highlighting to work in any context (within a .scm file or embedded scheme code in an .ly file). One thing I noticed was that (at least on the windows binary), vim\syntax\ did not contain a scheme.vim file, and neither does the syntax\ directory that ships with Git for Windows, C:\Program Files\Git\share\vim\vim73\syntax\. I found a scheme.vim online here: http://vim.cybermirror.org/runtime/ftplugin/scheme.vim ...copied that into both directories mentioned above, and still nothing. I'm using msysgit 1.8.3 from here: http://code.google.com/p/msysgit/downloads/list?q=full+installer+official+git Any ideas? Thanks. - Mark ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: second+ voice cross-measure slur problem
Am 29.07.2013 08:21, schrieb Papanastasiou Spyridon:
I'm not top posting.
\version 2.16.2
\new Staff {
{\voiceOne a1}\new Voice {\voiceTwo c1(}
{\voiceOne a1}\new Voice {\voiceTwo c1)}
{\voiceOne a1(}\new Voice {\voiceTwo c1}
{\voiceOne a1)}\new Voice {\voiceTwo c1}
}
the first slur is not connected
It is because you are using a polyphonic construct where the _first_
voice is considered a contigious voice while the second is instantiated
only during that polyphonic section.
Maybe this post on lilypondblog.org can help you understand the issue?:
http://lilypondblog.org/2013/07/voice-contexts-in-temporary-polyphonic-sections/
HTH
Urs
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
