FindGlobals, Lua 5.2, NppExec and pipe char

[Ketho]

I didn't want to derail this thread, and I have some questions about FindGlobals concerning Lua 5.2 and NppExec

1. Why does this cmd script give an empty output with Lua 5.2? But it still seems to work for Lua 5.1
   

   luac52 -l -p MyFile.lua | lua52 globals.lua MyFile.lua

   
   
2. Why doesn't NppExec support the pipe char | ? Or do I need to escape it or something in NppExec?
   
   This works fine in the Windows command line ...
   

   luac51 -l -p MyFile.lua | lua51 globals.lua MyFile.lua

   
   ... but this won't work in NppExec ...
   

   luac51 -l -p "$(FULL_CURRENT_PATH)" | lua51 "D:\FindGlobals\globals.lua" "$(FULL_CURRENT_PATH)"

   
   ... and the NppExec console gives the following error:

   luac51 -l -p "D:\World of Warcraft\Interface\AddOns\ScrollingChatText\ScrollingChatText.lua" | lua51 "D:\FindGlobals\globals.lua" "D:\World of Warcraft\Interface\AddOns\ScrollingChatText\ScrollingChatText.lua"
   Process started >>>
   luac51: cannot open |: Invalid argument
   <<< Process finished.

Notes:

• Shortened the cmd directory paths for readability
• lua-5.2.1_Win64_bin and lua5_1_4_Win64_bin paths added to Windows environmental variables

[Torhal]

I've never dealt with Lua 5.2 nor NPPExec, so no idea...:/

[Seerah]

Just to be clear to anyone reading this, WoW doesn't use Lua 5.2. It's on 5.1.

[cremor]

No idea about Lua 5.2 but I'm using NppExec as explained in the comments here: http://www.wowace.com/addons/findglobals/

[Ketho]

Originally Posted by cremor No idea about Lua 5.2 but I'm using NppExec as explained in the comments here: http://www.wowace.com/addons/findglobals/

I followed your advice and am doing it from the .bat now and referring to it from NppExec, and it works now!

Really curious why it doesn't work straight from NppExec though ..

For reference (for myself):

"D:\FindGlobals\globals.bat" "$(FULL_CURRENT_PATH)"

luac51 -l -p %1 | lua51 "D:\FindGlobals\globals.lua" %1

[tanz2014]

Originally Posted by Ketho I followed your advice and am doing it from the .bat now and referring to it from NppExec, and it works now! Really curious why it doesn't work straight from NppExec though .. For reference (for myself): "D:\FindGlobals\globals.bat" "$(FULL_CURRENT_PATH)" luac51 -l -p %1 | lua51 "D:\FindGlobals\globals.lua" %1

I know this thread is old, but just wanted to satisfy the curiosity ...

The functionality of the pipe operator (which is to redirect the standard output of the left-hand-side command as the standard input of the right-hand-side command) is supported by the Windows Command Shell (cmd.exe), not by NppExec. So if you do it from the .bat file it works because the .bat file is run by cmd.exe.

Alternatively you could have done the following from within NppExec:

cmd /c luac51 -l -p "$(FULL_CURRENT_PATH)" | lua51 "D:\FindGlobals\globals.lua" "$(FULL_CURRENT_PATH)"

which would start a cmd.exe with the rest of the command line, so the pipe would still work as expected.

[Ketho]

Thanks very much for the explanation and example, tanz2014 (and still satisfying my curiosity)

I also noticed that in my case I renamed my "lua5.1.exe" windows binary to "lua51.exe", I got annoyed by the dot I think. Just a friendly notice for others copypasting this...