Re: Methods of working

#ifdef style conditionals had already been rejected multiple times. That was circa 1.6, before the \tag command, which I confess I still haven't tried. Is there a way to filter tags from the lilypond command line? ~ John Williams ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user

wrapping long textual markup

t are long and measures are short, and if the measure it starts in is near the end of the staff line, half of the text falls off the side of the page. Can anyone give me some advice on how to get the text to wrap with the lines of music, without aligning the words to specific notes. ~ Joh

Re: wrapping long textual markup

t mind hacking at it a bit. But since lilypond is mixture of 4+ languages, it would be helpful if you could point me in the right direction... ~ John Williams ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user

text markup for long multi-measure rests

thing like that should be added to multi-measure-rest-text.ly. ~ John Williams ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user

Re: text markup for long multi-measure rests

this, if anyone is interested.) < R1*18 s_"Allegro" > So I wonder why the effort to add textscripts to multi-measures rests if they only work with single-measure multi-measure rests, and the < R s > workaround already provides more (although somewhat flawed) funtion

StemTremolo too short

This is a relatively minor nit, but I'm doing some 32nd note tremolos (d2:32). The downward stems look fine, but the upward stems look a little too short. The bottom tremolo stripe collides with the note head. Does anyone know of a way to fix this? ~ John Wil

Re: feature or bug

Try the latest CVS. Han-Wen just fixed a very similar bug for me, and it probably fixed your problem too. R1_"Text" was colliding with the bottom of the staff. ~ John Williams On 12 Apr 2003, David Bobroff wrote: > In this example using v1.7.16 CVS, the text over the notes

Lilypond security

reach down into the scheme, TeX, or postscript levels. Ghostscript has the -dSAFER option to prevent most exploits. I doubt TeX can do anything bad. But the scheme level makes me very uneasy. ~ John Williams ___ Lilypond-user mailing list [EMAIL

Staff vertical extent in lilypond-book

\lyrics { al -- lein al -- lein al -- lein } ~ John Williams ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user

Re: 6/4 rests

r1 is a rest of length 1 (= 4/4), but you want 6/4. Try R4*6 for a single rest which fills the measure. On Thu, 1 Jan 2004, Aaron wrote: > Hi all, > I just enter a trio which has a number of time changes. When I have > rests in 5/4 or 6/4 measures, like measures with whole rest or combos > th

Re: 6/4 rests

rity over the measure marks, which is why | only gives a warning if it's in the wrong place. And as Arvid pointed out, R1. is probably better than R4*6. ~ John Williams ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user

constructive criticism

taff" automatically creating a new Staff context, it would store the setting somewhere, so that new Staff contexts created in the same scope could inherit their default values from it. ~ John Williams ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user

Re: Lilywishlist was:Re: constructive criticism

Or better yet, a Wiki that users can easily add to. Maybe primed with the lilypond docs. It would have to know how to filter through lilypond-book though... On Mon, 5 Jan 2004, Aaron wrote: > In the same vein a FAQ would also be nice. By FAQ there are some > questions asked many times on the ma

Re: constructive criticism

e answers are yes, then I think it is a very good idea. I like the idea of being able to attach things to Contexts similar to how we attach articulations to notes. ~ John Williams ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user

Re: constructive criticism

iki approach allows the users to directly change and extend the manual. I suspect it would improve faster, but you lose some control over it. Wikis keep a history, so you can undo changes if needed. It would also need some customization to work with lilypond-book. ~ John Williams _

Re: constructive criticism

Han-Wen Nienhuys wrote: > Why not edit the texinfo source directly, and send a patch? You are asking the users to learn texinfo, diff and patch before they can help you. And as someone else pointed out, if they install a prebuilt version, they don't even have the texinfo source. (Personally, gnu

Re: constructive criticism

t which fetched the wiki page. (preferably without the wiki headers and footers) ~ John Williams ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user

property syntax (was Re: constructive criticism)

\with { % or \apply ? \set Staff.systemStartDelimiter = #'SystemStartBrace \set Score.RehearsalMark.padding = #1.5 } What do you think of that, Han-Wen? It's not new functionality; just simplifying the syntax. ~ John Williams ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user

Re: praise (and a sample)

future): the centered object (e.g., coda sign) and ... If no one replied about putting objects above barlines yet, the trick is to use \mark to do it. \mark\markup{ \musicglyph #"scripts-coda" } Although, I agree that your syntax for attaching things to barlines would

Re: example files (was "Re: SATB 2-staff template and request for suggestions")

piece details page, and not Chris Sawer unless the maintainer cannot be reached. ~ John Williams ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user

latin1 characters with lilypond-book -f html

this with an html source file? ~ John Williams ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user