feat: make elevating process in execution an option #485
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If
GlazeWM
isn’t run with administrator privileges, it can't handle certain windows properly (#456 ). However, runningcmd.exe
or any other programs in an elevatedGlazeWM
will cause it to be opened with elevated permission as well.I've attempted a (somewhat ugly) trick by using
explorer.exe
to open a shortcut of the program, allowing the target process to remain unelevated.But there are still two aspects I believe need consideration:
temp.lnk
? Although launching the new program occurs in a separate process, to avoid potential issues,GlazeWM
's main process still waits forexplorer.exe
to finish before deletingtemp.lnk
. This might slightly increase program startup time. Iftemp.lnk
isn’t deleted (I'm unsure if users would be concerned about it), none of the aforementioned issues would arise.exec cmd.exe
spawns an unelevated process, whilesudo exec cmd.exe
invariably spawns an administrator process, regardless of whetherGlazeWM.exe
has elevated privileges.