|
From: | Auto mailings of changes to Lily Issues |
Subject: | [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4908 Make \header blocks tangible in Scheme |
Date: | Sun, 17 Jul 2016 16:16:36 +0000 |
[issues:#4908] Make \header blocks tangible in Scheme
Status: Verified
Labels: Fixed_2_19_45
Created: Tue Jun 28, 2016 09:11 AM UTC by David Kastrup
Last Updated: Thu Jul 07, 2016 04:25 PM UTC
Owner: David Kastrup
Make \header blocks tangible in Scheme
This treats Guile modules and \header blocks as more or less
equivalent. Since \header blocks also contain module imports that
might not concur with those at the place of use, any use of a module
in place of a \header merely copies the values of the module
variables. Consists of the commits:
Admit \header-like _expression_ into \score
Admit \header-like expressions in \header
Admit \header-like expressions at top levels
\header-like expressions are allowed at \book, \bookpart,
and top level.
Allow \header blocks in expressions
This allows creating modules for further programmatic manipulation.
http://codereview.appspot.com/296600043
Sent from sourceforge.net because address@hidden is subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev
_______________________________________________ Testlilyissues-auto mailing list address@hidden https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Prev in Thread] | Current Thread | [Next in Thread] |