Terminal app appears unexpectedly and runs code

Question

RYz Author

Level 1

23 points

Terminal app appears unexpectedly and runs code

Terminal keeps appearing for me sometimes when I'm working in the desktop. Sometimes it just says:

"

No manual entry for folder

[Process completed]

"

which seems to be harmless, but I'm hoping to disable whatever key combo does that.

But this time it appeared when I opened a file by accident, and ran some code. I have no idea if this code did anything to my computer. The file originally had a .gfx extension but I had typed a note to myself in the name after that.

I have a screenshot of the output it gave that time, should I upload that or is there a log I can view somewhere?

iMac (M1, 2021)

Posted on Nov 26, 2025 3:48 PM

Reply

Answer 1

Nov 26, 2025 6:03 PM in response to RYz

It’s being interpreted as a shell script, or is locally set as a shell script, and it’s not.

BBedit and other options exist for editing, as well.

You can set this file or GFX files generally to open with TextEdit, BBEdit, MacVim or otherwise, using Get Info in Finder.

Reply

Answer 2

Nov 26, 2025 3:58 PM in response to RYz

What happened depends on what file was clicked, snd in what the file contains.

Various (different) apps can create and process (different) GFX files. What apps are you using these GFX files for?

Wouldn’t expect a typical GFX file that opens a terminal session to do much past showing errors.

The error looks like something is trying to invoke a man command, and failing.

Reply

Answer 3

RYz Author

Level 1

23 points

Nov 26, 2025 5:57 PM in response to MrHoffman

It was a fonts.gfx file from Stellaris. I was trying to change what the font colors were. I was supposed to open the file in TextEdit but I accidentally did some sort of key combo with Command-ArrowKey I think.

It looks like something did happen at line 24, which was:

W = { 255 255 255 } # W = White.

there's a whole load of

"bitmapfont = {"

and

"bitmapfont_override = {"

code below that which I don't see any errors for in the Terminal output.

Reply

Answer 4

RYz Author

Level 1

23 points

Nov 28, 2025 9:00 AM in response to MrHoffman

My main concern is what this script might have changed in my computer/system.

Could it have changed something?

Side note: I've added a new .gfx after my notes in the filenames of these files, which did put the icon back to a blank document rather than a black box with green text. Hopefully opening it by accident won't run code again.

Reply

Answer 5

Nov 28, 2025 9:25 AM in response to RYz

RYz wrote:

My main concern is what this script might have changed in my computer/system.

Could it have changed something?

Side note: I've added a new .gfx after my notes in the filenames of these files, which did put the icon back to a blank document rather than a black box with green text. Hopefully opening it by accident won't run code again.

Without reviewing the script itself, and whatever else might be triggering, who knows?

A graphics file triggered as a script is unlikely to do anything, much less cause damage, barring unusual or nefarious circumstances.

Reply