[doc fact-check] variables in lilypond scheme

2006-10-23 Thread Graham Percival
Should variables in define-music-function have #s ? padText = #(define-music-function (parser location padding) (number?) #{ % Both of these lines work. Which should be in the docs? % \once \override TextScript #'padding = $padding \once \override TextScript #'padding = #$padding #}) \rel

Re: Chromatic staff

2006-10-23 Thread kevin
Thanks for the response. Changing the line-count sounds simple. After you mentioned this, I found the relevant documentation already open in browser, though previously invisible. I'm still trying to get a handle on the Lilypond documentation for more abstract areas. The idea of modifying the pit

Re: lilypond on FreeBSD?

2006-10-23 Thread Edward Sanford Sutton, III
On Saturday 21 October 2006 00:55, Jan Nieuwenhuizen wrote: > We base the FreeBSD binaries on 4.10-RELEASE-p2. Would it make > sense to support 6.x as well? If so, we need a binary of > the c library to bootstrap the build Version 4 is about as far back as any updates go into FreeBSD right now

Re: [bug] bad size of piano brace

2006-10-23 Thread Han-Wen Nienhuys
Phillip Kirlin escreveu: All, Just thought I'd echo this sentiment on the piano brace, they all seem to be displaying too small in any document that uses a PianoStaff (including the 2.9 documentation online). Example: (straight from http://lilypond.org/doc/v2.9/Documentation/user/lily-58088

Re: [bug] bad size of piano brace

2006-10-23 Thread pkirlin
I'm confused. I think it's still broken; I just downloaded and tested 2.9.26-2, and it's still giving me too-small piano braces. --Phil Quoting Juergen Reuter <[EMAIL PROTECTED]>: > > Right. Though, afterwards I noticed that the bug obviously had already > been fixed when I reported it; only

Re: [bug] bad size of piano brace

2006-10-23 Thread Juergen Reuter
Right. Though, afterwards I noticed that the bug obviously had already been fixed when I reported it; only the online Documentation is slightly outdated. Sorry for the unnecessary uproar! Greetings, Juergen On Mon, 23 Oct 2006, Phillip Kirlin wrote: All, Just thought I'd echo this senti

Re: [bug] bad size of piano brace

2006-10-23 Thread Phillip Kirlin
All, Just thought I'd echo this sentiment on the piano brace, they all seem to be displaying too small in any document that uses a PianoStaff (including the 2.9 documentation online). Example: (straight from http://lilypond.org/doc/v2.9/Documentation/user/lily-580882106.ly) \new PianoStaf

Re: lilypond on FreeBSD?

2006-10-23 Thread Jan Nieuwenhuizen
Ian Stirling <[EMAIL PROTECTED]> writes: >> What library is that? > > /usr/libexec/ld-elf.so.1: Shared object "libm.so.2" not found, required by > "lilypond" > /usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found, required by > "lilypond" > > By using quick and dirty symbolic links poi

Re: Chromatic staff

2006-10-23 Thread Mats Bengtsson
Getting a 4 line staff is trivial, just add \override Staff.StaffSymbol #'line-count = #4 at the beginning of your stave. You can also make this setting apply to all Staff contexts, see the documentation. For the vertical position, one idea would be to implement a music function in Scheme that m

Chromatic staff

2006-10-23 Thread Kevin Dalley
I know that alternative notation and chromatic staffs comes up once in a while. Let's choose a simple one, and assume that I can write some C++, Python, and Scheme. How would I change the notation to using 6-6 Tetragram? http://web.syr.edu/~pwmorris/www.mnma.org/gallery/4LineNotations.html Th