Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NirLauncher relying on Chocolatey shims causes some weird issues #235

Open
God-damnit-all opened this issue Apr 20, 2023 · 1 comment
Open

Comments

@God-damnit-all
Copy link

I've noticed things that shouldn't be launching with a command line keeping a command line window open, and this also makes NirLauncher's Explorer Copy feature worthless since it will just copy the shim instead.

I think it would be better to have the sysinternals nlp in the Launcher directory and insert the direct path to the tools into the nlp file. This can be programatically determined by running one of the Sysinternals shims with --shimgen-noop and using the second line, the one that says path to executable:. Running on each and every shim shouldn't be necessary, just taking the path from one and using it for the rest would suffice.

@majkinetor
Copy link
Owner

Yeah, I can do that when the package gets allowed to proceed. I wouldn't count on that though, but there is nothing I can do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants