Broken Windows command check #62
Comments
jgmdev
added a commit
to jgmdev/lsp
that referenced
this issue
Feb 14, 2024
Besides checking for .exe files we now check for .cmd and .bat files as reported on lite-xl/lite-xl-lsp#62 This commit also: * Uses new system.setenv to add /usr/local/bin to path if missing on MacOS * When logging using utils check if log file was successfully opened before trying to write into it. * If value returned by os.getenv is nil set result to empty string
jgmdev
added a commit
to pragtical/lsp
that referenced
this issue
Feb 14, 2024
Besides checking for .exe files we now check for .cmd and .bat files as reported on lite-xl/lite-xl-lsp#62 This commit also: * Uses new system.setenv to add /usr/local/bin to path if missing on MacOS * When logging using utils check if log file was successfully opened before trying to write into it. * If value returned by os.getenv is nil set result to empty string
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On Windows, these extensions are executable: .exe, .bat, .cmd. However, symbolic links to executables are also executable, so stuff like
lite-xllinked to lite-xl.exe is automatically executable.There is not a good way to do this unless relying on a Win32 function. But I think these extensions should be considered as well.
The text was updated successfully, but these errors were encountered: