Making only some Lua scripts on the path runnable from the command line in Windows XP

0
votes

Note: this trick also applies to scripting languages other than Lua, or to any other document type that might be considered an application in some contexts and a document in others.

If an interpreter is already associated to handle .lua files in Windows (i.e. if double clicking on a .lua file runs it in the interpreter) it is easy to make them executable directly on the command line.

You need to:

  1. put the script in a directory that is listed in the PATH environment variable;
  2. add the .lua extension to the PATHEXT environment variable.

In this way you can run any Lua script by typing its name on the command line. The problem now is that you cannot put another Lua script in any directory on the PATH without risking it to be executed, even if you don't want it to be executed. (An example of such a .lua file would be a module private to your program that will be loaded by require. Modules are by convention also named .lua, but rarely support execution as a free-standing program.)

So it is an all-or-nothing situation. Either you allow any script in a directory on the path to be executed or none.

Is there a way to allow only some scripts in a directory on the path to be runnable typing their name?

1
windowsscriptingluaconsolepath-variables
If you have answered your question, then post the answer as an answer, not as part of your question. - Nicol Bolas
As I have said in the post I could not answer as an answer, I have too low a rep! I have to wait 8 hours. It was the SO interface itself that, when trying to answer, told me I couldn't do that and to edit the question instead! Why did you erase the answer while I only followed what SO interface told me to do? - Lorenzo Donati -- Codidact.com
Oh, well. I'll try again. It seems my rep has already gone up. I'm still a newbie here. Sorry if I broke some rules. - Lorenzo Donati -- Codidact.com
I'm resisting the temptation to remove the Lua tag because Lua is really only the context for discussion of a quirk of Windows CMD.EXE name resolution using PATHEXT. The same trick applies to any other interpreted language or really any other file type. - RBerteig
@RBerteig I see. Effectively since I'm a newbie on SO I wasn't sure whether I should have put that only under the scripting umbrella. Since my use case was essentially that of Lua and the examples provided were about Lua I decided to use Lua tag for fear that without it the community could flag the post as off-topic or not well documented (my initial note reflects this mixed feeling). - Lorenzo Donati -- Codidact.com

1 Answers

2
votes

The trick is that the console PATHEXT mechanism understands "double extensions", i.e. adding a .exe.lua "extension" to PATHEXT will make executable only those Lua scripts which have their full-name ending in .exe.lua (of course you can choose another extension, say .run.lua). Note: I used the quotes to avoid possible confusion and for lack of better terminology (remember that, conventionally, the file extension is the part of the file name after the last dot).

Therefore by adding .exe.lua to PATHEXT only whatevername.exe.lua will be executable, whereas any other Lua script won't (provided it doesn't have the same "double extension").

This allows to distinguish "normal" scripts from "executable" ones without either separating them in different directories or define a new custom file extension, which involves modification to the registry.

Moreover since this behaviour is controlled by an environment variable, it is a per-process setting - you can enable it only for a specific console window. For example if you create a batch file with this content:

@set PATHEXT=%PATHEXT%;.exe.lua &cmd /K

and you run it, it will open a console that will be able to execute all .exe.lua scripts found on the path, but not any other .lua script.