I found this discussion because I'm having the same issues. Either (1) the button looks like I want it to and has the right label but is always at the end, or (2) the button looks like I want it to and resides where I want it to but says "Python Script 1" when I hover over it. Maybe the onhover label could be the script name?
I've been looking at this for days, but didn't see "Be able to run wsl / bash from a 32 bit process" until a little while ago. The key statement was "I simply copied bash.exe from c:\windows\system32 to c:\windows\syswow64. This worked. now, I can launch bash.exe from the 32 bit command shell." I copied wsl.exe instead, and can now run sed, etc from within my NppExec script.
I've got a very simple NppExec script that tries to use "sed" from WSL to clean up the output of a Windows command. The first two lines show the problem. C:\Windows\System32\cmd.exe /C net use > C:\Users\user1\Downloads\netuse.tmp C:\Windows\System32\cmd.exe /C C:\Windows\System32\wsl.exe sed -i 's/Microsoft Windows Network//g' /mnt/c/Users/user1/Downloads/netuse.tmp The first line runs fine in the script, and the file is generated. And the second line runs fine from an actual Command Prompt window...
I've got a very simple NppExec script that tries to use "sed" from WSL to clean up the output of a Windows command. The first two lines show the problem. C:\Windows\System32\cmd.exe /C net use > C:\Users\user1\Downloads\netuse.tmp C:\Windows\System32\cmd.exe /C C:\Windows\System32\wsl.exe sed -i 's/Microsoft Windows Network//g' C:\Users\user1\Downloads\netuse.tmp The first line runs fine in the script, and the file is generated. And the second line runs fine from an actual Command Prompt window and...
I've got a very simple NppExec script that tries to use "sed" from WSL to clean up the output of a Windows command. The first two lines show the problem. C:\Windows\System32\cmd.exe /C net use > C:\Users\user1\Downloads\netuse.tmp C:\Windows\System32\cmd.exe /C C:\Windows\System32\wsl.exe sed -i 's/Microsoft Windows Network//g' C:\Users\user1\Downloads\netuse.tmp The first line runs fine in the script, and the file is generatd. And the second line runs fine from an actual Command Prompt window and...
I've got a very simple NppExec script that tries to use "sed" from WSL to clean up the output of a Windows command. The first two lines show the problem. C:\Windows\System32\cmd.exe /C net use > C:\Users\user1\Downloads\netuse.tmp C:\Windows\System32\cmd.exe /C C:\Windows\System32\wsl.exe sed -i 's/Microsoft Windows Network//g' netuse.tmp The first line runs fine in the script, and the file is generatd. And the second line runs fine from an actual Command Prompt window and removes the text. But when...
I think I opened this issue for the wrong application? This is not the main NPP ticket system, but rather Notepad++ Plugins? Sorry. Please close.
"Run until the end of file" only runs once