TeXShop LuaLaTeX engine issues

[Noah Lovins]

Salvete, I just installed MacTeX and TeXShop on my Mac at home today, Mac OS Ventura. Followed the configuration instructions from the GitHub to the teeth, but when I go to typeset, I get a message saying that the engine does not have the executable bit set. Not really sure what this means.

Any help is appreciated, gratias vobis

- Noah

[Matthias Bry]

Salve,

Vide https://tex.stackexchange.com/questions/688995/cant-typeset-after-updating-texshop-xelatex-engine-does-not-have-the-executab

In Christo, 

Matthias 

--
Gregorio homepage: http://gregorio-project.github.io
Archives for the old mailing list: http://www.mail-archive.com/gregori...@gna.org/
To report a bug, please post to: https://github.com/gregorio-project/gregorio/issues
---
You received this message because you are subscribed to the Google Groups "Gregorio Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gregorio-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/gregorio-users/72569b28-6011-4353-acad-6c837ff47199n%40googlegroups.com.

[Noah Lovins]

No luck there either, but did get some new error messages too.

\documentclass[11pt]{article}

\usepackage{fontspec}

\usepackage[autocompile]{gregoriotex}

\begin{document}

\gregorioscore{orinchristmas}

\end{document}

[Matthew Roth]

I had a lot of problems with later updates to Ventura. I assume that if you are on Ventura you can’t upgrade further?

If I recall correctly, I redid the score files, checked for invisible characters, changed directories… and one thing that probably would have helped, which I didn’t know to do, was to delete the auxiliary files. TeXShop does this if you use its terminal window and hit the tab that offers exactly that.

Also as an aside: I use latexmk which (mostly) retypesets as needed. Useful for correct line spacing, making braces for psalmody, etc. It also is needed if you have a book and reference material elsewhere, create an index, etc.

It’s easy to do in TeXShop. I believe may have to check the engine folders, but once you do, a whole new world opens up.

Put this at the top of your documents once you do that. 

% !TEX TS-program = lualatexmk

% !TEX parameter = --shell-escape

To view this discussion visit https://groups.google.com/d/msgid/gregorio-users/a9964e8c-b1f0-4b0c-831a-7bb583b5a7d9n%40googlegroups.com.

[Noah Lovins]

I hadn’t thought about that, I think I could upgrade, I just haven’t thought to do it since I use this computer so infrequently. I’ll try again after updating.

-Noah

On Jan 31, 2025, at 10:37, Matthew Roth <roth.m...@gmail.com> wrote:



You received this message because you are subscribed to a topic in the Google Groups "Gregorio Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gregorio-users/xJRbwCq8zIE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gregorio-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/gregorio-users/CAEyUHDfXbOuuPoSCEHPFZ9Z6JVscujNSr%2BQ9kyqbqktvWK-zoA%40mail.gmail.com.

[Noah Lovins]

Updated to Ventura 13.7.3 which is up to date. Still getting the same error in the console. It sounds to me like the engine itself is busted unless I'm mistaken.

-Noah

[rled...@gmail.com]

I had a similar problem trying to run from an editor on a Linux system. It would compile fine from the command line but not from within the editor. If it works from the command line for you then it may be a similar issue. 

Alas, I was unable to find a fix.

Regrettably this is all a little over my head, so I hope my explanation is at least partially helpful.

Turns out it was a security ‘feature’. The shell (run time environment - the ‘shell escape’ bit) that started when I clicked compile in the editor did not preserve the environment variables from my current user environment that pointed to the Tex installation, etc, so running from the editor couldn’t find stuff. Running from the command line used my actual user shell with the environment variables in place so things worked.

It’s apparently viewed as dangerous to allow this kind of shell escape thing with a program that has a lot of access rights.  And yet it is necessary in this sort of Tex setup.

Hope this at least sheds some light on what might be going on.

Rob Leduc 

No dia 31 de jan. de 2025, às 1:21 PM, Noah Lovins <noahlov...@gmail.com> escreveu:

Updated to Ventura 13.7.3 which is up to date. Still getting the same error in the console. It sounds to me like the engine itself is busted unless I'm mistaken.

To view this discussion visit https://groups.google.com/d/msgid/gregorio-users/1bfc687c-edbd-494f-8515-fd312eb717f8n%40googlegroups.com.

<Screenshot 2025-01-31 at 12.20.19 PM.png>

[R. Padraic Springuel]

Please run our system-setup.command script system-setup.bat on Windows) and post the results here. The script is available in the contrib directory of your Gregorio installation or can be downloaded: https://github.com/gregorio-project/gregorio/tree/master/contrib

✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
Fr. Samuel, OSB
(R. Padraic Springuel)
St. Anselm’s Abbey
4501 South Dakota Ave, NE
Washington, DC, 20017
202-269-2300
(c) 202-853-7036

PAX ☧ ΧΡΙΣΤΟΣ

On Feb 1, 2025, at 9:04 AM, rled...@gmail.com wrote:



To view this discussion visit https://groups.google.com/d/msgid/gregorio-users/B12BCD11-6829-4704-B996-E153803FBB7C%40gmail.com.

[Noah Lovins]

Does that script need to be in a specific directory before running it?

[Noah Lovins]

This is what we end up with when trying to open it. Sharing and permissions in get info say I can read and write. 

-Noah

[Fr. Samuel Springuel]

Two possibilities:

1) You don’t have the executable bit set on the file. To fix this open Terminal and cd to the folder containing the script and execute `chmod +x system-setup.command`.
2) macOS has become much more paranoid about security over the years and quarantines downloaded files to prevent you from accidentally running potentially hazardous code downloaded from the Internet (or less favorably, is trying to force you to stick with App Store apps where Apple get’s their cut of the revenue). To remove the quarantine, you need to open Terminal and cd to the folder containing the script and execute `xattr -d com.apple.quarantine system-setup.command`

In either case, once you’re in Terminal at the right folder, you might as well execute the script from there rather than double clicking on it in Finder. Just type: `./system-setup.command`

Output will be saved to system-setup.log in the same folder.

✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝

Fr. Samuel, OSB
(R. Padraic Springuel)
St. Anselm’s Abbey
4501 South Dakota Ave, NE
Washington, DC, 20017
202-269-2300
(c) 202-853-7036

PAX ☧ ΧΡΙΣΤΟΣ

> To view this discussion visit https://groups.google.com/d/msgid/gregorio-users/63a346da-54dc-410e-ba35-7bc86514f4fdn%40googlegroups.com.
> <Screenshot 2025-02-01 at 12.25.23 PM.png>

[Noah Lovins]

Thank you Father. Upon running the command in Terminal, we got this log.

-Noah

[Kelvin Sandigo]

I cannot find the words to express my gratitude for finding this thread. I started my Gregorio journey in late 2022 on Windows 10 with a full install of TeX Live and using TeXworks as the editor. Then in early 2023 I started using Ubuntu 22.04 as my on-and-off daily driver. With some help from this thread, I replicated my TeX Live and TeXworks setup as I had it on Windows.

When I upgraded to Ubuntu 23.10 in late 2023, TeXworks would not compile the chant and gave me the same "Unable to find gregorio executable. shell-escape mode may not be activated." error. I uninstalled and reinstalled Tex Live and TeXworks, I upgraded to Ubuntu 24.04, and all to no avail. I threw up my hands and resigned to running Gregorio on Windows 10 (which always worked).

Just in the past month (April 2025) I installed EndeavourOS (Arch-based Linux distro) on an old laptop. I wanted to give Gregorio another try on a "new" machine and, alas, the same error came up from TeXworks. Then Rob Leduc gave me the idea to just run the compiling step through the command line. So logged in to my admin profile and simply running 

lualatex --shell-escape low_off.tex 

in a terminal in the folder where I have all my files produced the PDF of the Low Sunday Offertory I prepared on TeXworks. I'm far from a computer expert, but my anecdotal experience may lend credence to the theory that some security patch was pushed on Unix / Mac systems that prohibit shell-escape to be run from applications but not from the terminal.

[rled...@gmail.com]

Glad to be of service.

What I found in Ubuntu was that the default shell started when escaping out of a program like an editor was something other than bash - I don’t recall which one. In that shell the environment variables were not preserved from the calling program so variables like $TEXMF were blank in that shell. So it literally didn’t know where the Tex installation was anymore. 

I imagine it is for our security but it is truly annoying in this case.

None of this is an issue from the command line since you’re running in your main shell.

I never did find a workaround. It seemed extreme to change the default shell for the whole operating system for this one use. I suppose some sort of script could be written to to replace /bin/sh or whatever with something that sets the Tex variables and calls the shell but I never tried it.

Good luck!

R

No dia 9 de mai. de 2025, às 1:19 PM, Kelvin Sandigo <kelvi...@gmail.com> escreveu:

I cannot find the words to express my gratitude for finding this thread. I started my Gregorio journey in late 2022 on Windows 10 with a full install of TeX Live and using TeXworks as the editor. Then in early 2023 I started using Ubuntu 22.04 as my on-and-off daily driver. With some help from this thread, I replicated my TeX Live and TeXworks setup as I had it on Windows.

To view this discussion visit https://groups.google.com/d/msgid/gregorio-users/9d098f43-ad3c-4212-8654-9f98eb291f5en%40googlegroups.com.