Re: \context + \set ineffective

2018-04-16 Thread Dan Eble
I’ve convinced myself that this is a bug, so I will spend some time trying to 
change it and see what happens.  I will probably use something like the 
following as regression tests.

Regards,
— 
Dan

\version "2.19.80"

\layout {
  indent = 0
  line-width = 2 \cm
}

%% Find the nearest enclosing context of some type.
\score {
  \new StaffGroup = "A" <<
\new StaffGroup = "B" \with { shortInstrumentName = "FAIL" } {
  e'1
  \context StaffGroup {
%% This is expected to replace FAIL.
\set StaffGroup.shortInstrumentName = "PASS"
  }
  \break
  e'1
}
  >>
}

%% Find the nearest enclosing context by type and ID.
\score {
  \new StaffGroup = "A" <<
\new StaffGroup = "B" \with { shortInstrumentName = "FAIL" } {
  e'1
  \context StaffGroup = "B" {
%% This is expected to replace FAIL.
\set StaffGroup.shortInstrumentName = "PASS"
  }
  \break
  e'1
}
  >>
}

% Create a new context by type and ID even though both match the
% enclosing context.
\score {
  \new StaffGroup = "A" <<
\new StaffGroup = "B" \with { shortInstrumentName = "PASS" } {
  g'1
  \new StaffGroup = "B" {
%% This does not replace PASS because it is a new context, and
%% it is not engraved because this context contains no music.
\set StaffGroup.shortInstrumentName = "FAIL"
  }
  \break
  g'1
}
  >>
}

% Find an enclosing context by type and ID when there is another
% context of the same type in between.
\score {
  \new StaffGroup = "A" \with { shortInstrumentName = "FAIL" } <<
\new StaffGroup = "B" {
  b'1
  \context StaffGroup = "A" {
%% This is expected to replace FAIL.
\set StaffGroup.shortInstrumentName = "PASS"
  }
  \break
  b'1
}
  >>
}


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Stem lenght and ledger lines

2018-04-16 Thread Malte Meyn



Am 16.04.2018 um 09:14 schrieb foxfanfare:

What exactly is Malte's new-flags?


I added 256th, 512th, and 1024th rest and flag glyphs to Emmentaler so 
that you can use these rests and the notes without beams, see issue 
5277: https://sourceforge.net/p/testlilyissues/issues/5277/


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Stem lenght and ledger lines

2018-04-16 Thread foxfanfare
Torsten Hämmerle wrote
> This is sheer coincidence - LilyPond always (!) extends the stems to the
> middle stave-line.
> As soon as there are more than two flags, they obscure the ledger lines.
> 
> Moreover, cue size note stems should not even extend to the middle
> stave-line but be a stave-space shorter, even when extended. Gould does
> not
> mention that explicitly, but one can see it in her examples.
> 
> I'm going to create an issue (and incidentally have already created a
> patch
> some time a go that still needs some testing for beams and tremolos).
> 
> Here's the current status showing cue notes in the lower staff and already
> using Malte's new mega-flags:
> 
> ; 
> 
> All the best,
> Torsten

Thank you for your interest!
What exactly is Malte's new-flags?



--
Sent from: http://lilypond.1069038.n5.nabble.com/Bugs-f58488.html

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond