On Mon, Sep 29, 2014 at 4:41 PM, Peter Crighton <petecrigh...@gmail.com> wrote:
2014-09-29 21:18 GMT+02:00 Federico Bruni <fedel...@gmail.com>:
2014-09-29 21:12 GMT+02:00 Abraham Lee <tisimst.lilyp...@gmail.com>:
Put the overrides in a \layout block, like:

\layout {
  \override TabStaff.Stemstencil = ##f
}

This won't create a new context, but it will apply it when you create one.

It's also a way to keep music and style separated.

Yes, I keep them separated as much as I can.
Putting this in a layout block won’t work here, though. I have extended \improvisationOn to work to my liking with TabStaffs:

improvisationOn = {
  \set squashedPosition = #0
  \override NoteHead.style = #'slash
  \override Accidental.stencil = ##f
  \override AccidentalCautionary.stencil = ##f
  \override TabStaff.Stem.stencil = ##f
  \override TabStaff.Flag.stencil = ##f
  \override TabStaff.Beam.stencil = ##f
  \override TabStaff.Dots.stencil = ##f
}

I can’t simply put a layout block in there.
So, now by calling \improvisationOn in a score without a TabStaff I came upon the undesired output.

--
Peter Crighton | Musician & Music Engraver based in Mainz, Germany
http://www.petercrighton.de

If it's something you need to be able to call on-demand, then put it in a scheme function (you might need another one to turn it off):

improvisationOn = #(define-scheme-function (parser location)
 #{
   (insert overrides here)
 #})

improvisationOff = #(define-scheme-function (parser location)
 #{
   (revert overrides here)
 #})


Regards,
Abraham
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to