On Sat, 24 Nov 2012 22:16:45 -0800, Keith OHara wrote:
\version "2.16.1"
<< \new Staff {
\once\set Staff.whichBar = "|:"
b2 b2 b2 b2
\once\set Staff.whichBar = ":|:"
b2 b2 b2 b2
\bar"|." }
\new Staff R1*4 >>
<< \new Staff {
b2 b2 b2 b2
\once\set S
On Sat, 24 Nov 2012 16:44:15 -0800, Thomas Morley
wrote:
2012/11/25 Keith OHara :
Ben Rudiak-Gould gmail.com> writes:
The 2.16 documentation says that \set Staff.whichBar = "|:" "will create a
start-repeat bar in this staff only".
I suppose desired behavior is to have at least one way to
2012/11/25 Keith OHara :
> Ben Rudiak-Gould gmail.com> writes:
>
>> The 2.16 documentation says that \set Staff.whichBar = "|:" "will create a
>> start-repeat bar in this staff only".
>
> I suppose desired behavior is to have at least one way to change one bar-line
> in one staff, preferably the w
Ben Rudiak-Gould gmail.com> writes:
> The 2.16 documentation says that \set Staff.whichBar = "|:" "will create a
> start-repeat bar in this staff only".
I suppose desired behavior is to have at least one way to change one bar-line
in one staff, preferably the way it was done in version 2.14
<
On Sat, Nov 24, 2012 at 10:13:25PM +, Ben Rudiak-Gould wrote:
> The 2.16 documentation says that \set Staff.whichBar = "|:" "will create a
> start-repeat bar in this staff only". What it actually seems to do in 2.16.1
> is
> insert a start-repeat bar after every note in that staff until the e
The 2.16 documentation says that \set Staff.whichBar = "|:" "will create a
start-repeat bar in this staff only". What it actually seems to do in 2.16.1 is
insert a start-repeat bar after every note in that staff until the end of the
score. I haven't looked at the code but I guess that it's clearing
2012/11/24 Eluze :
>
> Am 24.11.2012 10:37, schrieb David Kastrup:
>
>> Since string numbers are otherwise used consistently, and since
>> fingerings of 0 are being used as well, and there is plenty of both
>> circled and uncircled 0, I am pretty sure that there is some meaning to
>> it. I just ha
Am 24.11.2012 10:37, schrieb David Kastrup:
Since string numbers are otherwise used consistently, and since
fingerings of 0 are being used as well, and there is plenty of both
circled and uncircled 0, I am pretty sure that there is some meaning to
it. I just have no idea _which_ meaning.
I sto
Il 24/11/2012 10:32, David Kastrup ha scritto:
We'd better use<> or {} ? The latter, I guess.
No, that's just masking the problem.
http://code.google.com/p/lilypond/issues/detail?id=2974>
contains a patch fixing this.
ok, thanks
___
bug-lilypond
Eluze writes:
> no way to conceal the errors made in this score - there is no string
> called "zero" and if it is a fingering indication (which it probably
> is) the circle shouldn't be there
Since string numbers are otherwise used consistently, and since
fingerings of 0 are being used as well,
Federico Bruni writes:
> If I specify an harmonic using \harmonicByFret or \harmonicByRatio,
> point-and-click works fine only if the note following the command is
> included inside <> or {}
>
> I think it's a bug in the documentation.
I don't think so.
> We'd better use <> or {} ? The latter,
David Kastrup wrote
> Thomas Morley <
> thomasmorley65@
> > writes:
>
>> 2012/11/23 Thomas Morley <
> thomasmorley65@
> >:
>>
>>> In printed editions of scores for the guitar I often saw StringNumber
>>> 0 indicating an open string.
>>
>> Example:
>> M.M. Ponce, "Sonata Romantica" 2nd movt.
>>
If I specify an harmonic using \harmonicByFret or \harmonicByRatio,
point-and-click works fine only if the note following the command is
included inside <> or {}
Otherwise, point-and-click opens ly/music-functions-init.ly, where these
commands are defined.
Try this snippet:
\version "2.17.
13 matches
Mail list logo