Greetings,
I installed the latest from git, made clean, autoreconf, configure, re-made,
and re-installed, fortunately on a test machine. I cannot get gregorio to work
with lulatex at all. The examples do not work either. When I run lualatex, I
get:
> ! Undefined control sequence.
> l.113 \grespaceabovelines
> =8mm
Now I saw that some of the commands have changed, but changing
grespaceabovelines to spaceabovelines does not work either. Similar error:
> ! Undefined control sequence.
> l.113 \spaceabovelines
> =8mm
>
This was a working installation of gregorio before this last update. A bit of a
loss at this point. Suggestions? Oh, and this is on OS X 10.10.2 with TexLive
2014 up to date.
---------------------------------------------------------------------
Michael Martin
[email protected]
Thesaurus Precum Latinarum
http://www.preces-latinae.org
----------------------------------------------------------------------
> On Mar 11, 2015, at 8:10 PM, Br. Samuel Springuel <[email protected]>
> wrote:
>
> The release has now been posted to the website.
>
> ✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
> Br. Samuel, OSB
> (R. Padraic Springuel)
>
> PAX ☧ ΧΡΙΣΤΟΣ
>
> On 2015-03-11 8:32 PM, Br. Samuel Springuel wrote:
>> This is a bug-fix/enhancement release which marks a significant shift in
>> the way that GregorioTeX deals with spaces internally and with how the
>> user interacts with them. For those who have been keeping up with the
>> changes on github, you may have noticed some of them already (a handful
>> made it into 2.4.2 silently).
>>
>> 1) All distances have a new naming convention which eliminates the
>> "\gre" prefix they used to have. When the user wants to refer to a
>> distance using one of the below described functions they simply enter
>> the name of the distance as a string. A complete list of the distance
>> names with descriptions is being prepared and will be released shortly.
>> Until then, please consult gsp-default.tex.
>>
>> 2) All distances have a new property, scaling, which determines whether
>> or not they scale when \grefactor changes. This property can be
>> manipulated directly via the commands \grenoscaledim and \grescaledim
>> which turn the behavior off and on respectively. By default all
>> distances have the property turned on.
>>
>> 3) Distances are set within a space configuration file (e.g.
>> gsp-myspaces.tex) with the \gresetdim command. This command takes three
>> arguments: the name of the distance, the value it is to assume (as a
>> string, not a TeX length register), and a numerical flag indicating
>> whether it should scale with \grefactor (1) or not (0). This command
>> does not ensure that the changes it makes propagate to all calculated
>> distances as that is done by the loading of the configuration file
>> (still done with \GreLoadSpaceConf). These distances can be set in em
>> and ex units and that choice should be respected at time of use (if you
>> find one that you think isn't, please let me know).
>>
>> 4) Space configuration files now require a \greconffactor to be
>> specified. All distances in the configuration file represent the actual
>> printed distance when the score is produced at the factor specified by
>> this value. See gsp-default.tex for an example of how to set it.
>>
>> 5) Distances can be changed within a project file by use of
>> \grechangedim. This command takes the same three arguments as
>> \gresetdim but will also ensure the propagation of the change to all
>> dependent calculations. As with \gresetdim, em and ex are permissible
>> units here.
>>
>> 6) The interface to adjust the thickness of the staff lines has been
>> overhauled. The command to change the thickness of the staff lines is
>> now \setstafflinethickness. This command takes one argument: an integer
>> which represents the thickness of the lines. This arguments scales in a
>> manner identical to \grefactor. That is, at \grefactor=17 (the default)
>> the staff line thickness is 17. At \grefactor=20 the staff line
>> thickness is also 20. If you want thinner lines, choose a number lower
>> than your \grefactor. For thicker ones pick something greater than it.
>>
>> 7) The functions for setting the spacing around the initial now take an
>> additional argument to indicate if these distances should scale with a
>> change in \grefactor. Their names are now: \setaboveinitialseparation,
>> \setspaceafterinitial, \setspacebeforeinitial, and \setinitialspacing
>> (no change for this last one). The old function names should still
>> work, but they will raise a deprecation warning and will assume that the
>> distances do scale (since they didn't take the new argument).
>>
>> 8) The behavior of the auto-compiler has been improved. It will now
>> automatically clean-up out dated files.
>
> _______________________________________________
> Gregorio-users mailing list
> [email protected]
> https://mail.gna.org/listinfo/gregorio-users
_______________________________________________
Gregorio-users mailing list
[email protected]
https://mail.gna.org/listinfo/gregorio-users
