I’m starting to use the KM action called “Execute Swift Script” (Although I’m barely capable of reading Swift scripts, I can still write some useful scripts using AI.) The problem with this action is that it’s slow because the action requires re-compiling the source every time you run it. This adds…

[image] DocOck: I do not disagree with your disagreement here. Please accept my apology. I hadn’t anticipated that the environment-creation was more significant than the compilation. Again -- don't believe me! Run your own tests. YMMV depending on OS, hardware, length of script, if you're sat…

[image] DocOck: Actually I was tinkering with an idea to make a macro that compiles the Swift code, and returns a filename of a compiled file. It might help me. That's what I've done—if you look at my App Launcher macro , you'll see that the macro checks if an invisible file exists before doin…

[image] griffman: This was my solution to make sure they always had it. Perhaps, instead, write a visible file into a directory in the user's Application Support folder? If nothing else it'll look a lot less suspicious!

[image] Nige_S: Perhaps, instead, write a visible file into a directory in the user's Application Support folder? If nothing else it'll look a lot less suspicious! Yea, probably a better spot and visible would be good. I'm just never sure where the macro would be allowed to write. Next time I…

[image] griffman: This was my solution Thanks for sharing that. Yet I’m inclined to write/create my own approach, because that makes me learn more. The creative process of coming up with unusual solutions is what I enjoy the most. Sometimes when I need Swift to be compiled, I need it to be c…

[image] griffman: The first step puts the code into a text file... Have you tried pumping the code in straight from the variable? You can use - for "read from stdin". Simple demo: [image]

In addition, you don’t even need to create a variable (if you don’t want to.) You can do the following instead. I’m using “-” for stdin in the middle of a shell command in this example. [image] Oops. I have to fix that! Sorry! Here it the correct version: [image]

[image] griffman: [image] Nige_S: Perhaps, instead, write a visible file into a directory in the user's Application Support folder? If nothing else it'll look a lot less suspicious! Yea, probably a better spot and visible would be good. Well, I already know where you won’t want to put …

[image] kevinb: Well, I already know where you won’t want to put that file . :grinning_face_with_smiling_eyes: The irony of all this is, with perfect hindsight, had you suggested Application Support, I would've been all in on that—it's the perfect spot for such files :). -rob.

[image] peternlewis: What happens after that and how long it takes is up to Swift. I want my Swift Scripts to run forever (they are mostly used to create popup windows that have a Close button) so I have to put them into an asynchronous macro that never ends. There’s a minor problem with that…

Keyboard Maestro Discourse

Suggestion: a modification to Execute Swift Script action

Questions & Suggestions

kevinb August 10, 2026, 9:21pm 15

Well, I already know where you won’t want to put that file.

Suggestion: a modification to Execute Swift Script action

Options