Help Verifying Install and Running GregorioTeX

[Andrew Nowrouz]

Hello, and happy Corpus Christi.

I tried using GregorioTeX for the first time yesterday on TeX Shop. I used the LuaLaTeX version in the drop down banner at the top of the editor’s interface. However, the compiler wouldn’t generate pdf’s. I am getting the error message: "restricted system commands enabled." [Screenshot 1]

I then dug around and now I am thinking that I don’t have Gregorio installed correctly.

I downloaded TeXShop and the entire TeX distribution through MacTeX in the Fall of 2022. I updated TeXShop today (6/8/23) and I believe my TeX Distribution is current. Thus, it seems that I should have the latest version of Gregorio, v. 6.0 from 2021. I am running a MacMini with Ventura 13.4.

However, when I go to “Configuring TeXShop for Gregorio,” I get confused by the following sentences:

1) "If you’re using the version of Gregorio that comes with TeXLive, then this should be done for you…”

Seems good, but,

2) If you have installed a version of Gregorio on top of the version that comes with MacTeX (an intermediate release or development version) then you will need to make use of an engine with the --shell-escape option active. Unfortunately, TeXShop does not come with such an engine configured by default. [Emphasis added]

So my question is, 1) do I need to use this “shell escape option,” or is my version of Gregorio good? I don’t how what “on top of the version” means.

If I do further installations… 2) how do I do that? I’ve read the following paragraph [screenshot 2] and my life is not easier.

Thank you for your time. I only included so many details to show that I’m trying all the options I can see, but I am not naturally tech savvy. God bless you.

[Andrew Nowrouz]

Update:

I believe I have found the correct file "LuaLaTeX+se.engine" on the GitHub page and installed it in the right location [screenshot 1].

However, now when I try to compile, I get the error message that the said engine "does not have the executable bit set" [screenshot 2].

Could this be referring to the auto configure command, found on the GitHub page?

[Andrew Nowrouz]

Update 2: Through much digging, and great counsel from a member here, I have added the proper engines to my TeXShop directory "under the hood" and have also made it executable through the Terminal.

I even ran one successful test, which was gratifying. (Yes, I know, the file source name is wrong.)

However, on my second attempt, I am effectively having the same problem, although now it is appearing in my console log. It is telling me that "shell-escape mode may not be activated." (!)

I don't know why I'm getting this particular message, especially the successful run before. All the right boxes seem to be checked off here. At the top of the console log, it even says "system commands enabled."

I think I am on the cusp of something. Progress has been good, but slow. Any final push will be most appreciated.

Thank you.

[Matthew Roth]

I also use this set-up. Good to see that it's working (well, sort of…). I wonder if Richard Koch (who is extremely helpful) would be amenable to including this engine in the default Inactive folder for new users… and fwiw, I virtually always add the magic comment via the Macros panel; I'm not gonna tinker with default engines, but I'll forget to change it when opening a file after a long time and working in a fog.

I don't know what is going on with the executable. With 13.3, I suddenly had issues opening files (including files with no special characters and glyphs which require Unicode in the file name). That seems to be gone, but sometimes something breaks, leading to "unable to find gregorio executable" and making the files locally (in a different directory if I don't change the name) is the only solution. It'll compile with a different name in the original directory, but if I delete the file downloaded from Gregobase and then rename my test file, it breaks again.

[Matthew Roth]

I'm still having issues with the "shell-escape mode may not be activated."

Really not sure what's going on here, so my debugging is less than helpful, but things aren't working as they ought.

[R. Padraic Springuel]

Please run system-setup.command and post the results here. You can download the script here:

✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
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 Jul 11, 2023, at 5:20 PM, Matthew Roth <roth.m...@gmail.com> wrote:

I'm still having issues with the "shell-escape mode may not be activated."

--
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 on the web visit https://groups.google.com/d/msgid/gregorio-users/95dcaeac-dc03-452f-a1a4-f1b0f69e9604n%40googlegroups.com.

[Matthew Roth]

So, in this case, it's fixed by removing spaces from the name of the tex file. I know that spaces cause issues, so I use dashes or underscores in m gabc files and for any tex files inserted via \input. Until now, I cannot recall having issues with the name of the score file and a space, but I'll avoid spaces entirely in the future.