Élie, do you have any suggestions for how to organize and label those additions?

✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
Br. Samuel, OSB
(R. Padraic Springuel)
PAX ☧ ΧΡΙΣΤΟΣ

> On Sep 15, 2015, at 2:50 AM, Élie Roux <[email protected]> wrote:
> 
> Le 15/09/2015 01:19, Conor Cook a écrit :
>> For the record, I am having the same issue on the command line — ! LaTeX
>> Error: File `luaotfload.sty' not found.
> 
> That's kind of good, because more experiments can take place and thus we
> can improve the diagnostic tool. Here are a few commands it would be
> useful to have the output of:
> 
> kpsewhich --all -engine luatex -progname lualatex gregoriotex.sty
> 
> kpsewhich --all -engine luatex gregoriotex.sty
> 
> kpsewhich --var-value=TEXINPUTS.lualatex
> 
> kpsewhich --var-value=LUAINPUTS.lualatex
> 
> BTW, it would be also useful to add these in the diagnostic tool, even
> though they're not relevant to Conor's case:
> 
> kpsewhich --var-value=shell_escape_commands
> 
> kpsewhich --var-value=openout_any
> 
> kpsewhich --var-value=openin_any
> 
> kpsewhich --var-value=shell_escape
> 
> Thank you,
> -- 
> Elie
> 
> _______________________________________________
> 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

Reply via email to