lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Manual volta placement and invisible barline kills previous barline


From: David Kastrup
Subject: Re: Manual volta placement and invisible barline kills previous barline
Date: Mon, 28 May 2012 14:08:26 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1.50 (gnu/linux)

"Philip Thomas" <address@hidden> writes:

> For example, some trials that didn't work included the following (the
> context is correctly Staff, I think, and not Score, because I moved
> the Volta_engraver from the Score to Staff context so that it would
> appear on each line in the vocal score):
>
> \override Staff.VoltaBracketSpanner #'X-extent = #'(1 . -1)
> \override Staff.VoltaBracketSpanner #'extra-X-extent = #'(1 . -1)
> \override Staff.VoltaBracket #'extra-X-extent = #'(1 . -1)
> \override Staff.VoltaBracket #'break-align-symbols = #'(clef)
> \override Score.KeySignature #'break-align-anchor = #3

[...]

> I must say that it feels a bit frustrating, after a while. I like
> using LilyPond, but I wish it was a bit less of a challenge at
> times. The piece I'm working on has repeats, but it is not in the
> nature of some avant-garde monster that will inevitably be difficult
> to tame. While I greatly appreciate the help of users on this forum --
> including you -- it is sometimes hard to escape the feeling that one
> can only get so far without being a programmer.

More like "without turning into a programmer".  If you take a look at
all the logic you applied and tested out ("the context is correctly
Staff, I think, and not Score, because I moved the Volta_engraver from
the Score to Staff context"), it is hard to claim that you are entirely
on the non-programmer side of the fence.

You are on the side of the fence where the power rests.  That is a good
thing in itself.  Unfortunately, there are also a lot of traps.  They
are not a consequence of the power as such, but they still need cleaning
out.  And that is an ongoing job.  You can help with that by making bug
reports from disappointed valid expectations.  The feedback will not
necessarily be immediate and/or satisfactory, and sometimes you might be
wrong.

I learnt climbing in Ith, an area which is bolted sparingly.  In
particular, whenever there is a natural feature (hole, hourglass,
chockstone, crack) you can use for protection, there is no bolt.  And
the distance between bolts tends to be on the scary side, anyway.  So
you learn to put additional protection where it will fit, getting a few
more meters of feeling comparatively protected.

I went up "Trunkene Mathematiker".  That one felt reasonably protected:
I did not get the "please don't let me fall" shiver so typical for
climbing in Ith.  It was back on the ground, talking the climb over with
the others that I realized there was not a single bolt apart from top
anchor.  So I had climbed my first "clean" ascent without realizing it
or mentally preparing for it.  But it was actually a less strenuous feat
than quite a few "bolted" routes.

LilyPond can't really keep you from becoming a programmer by and by.
But the experience should not be as painful.  Having things working
smoothly and according to reasonable expectations is not really what
distinguishes an environment for programmers from non-programmers.

You get more ways in which things may go wrong, but that does not mean
that they should.

-- 
David Kastrup




reply via email to

[Prev in Thread] Current Thread [Next in Thread]