Question: Alias with admin permission
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 27k
- Forks
- 2.1k
- PR merge metrics
- No merged PRs in 30d
Description
Question
Hello,
until recently I had an older CMDER version installed (unfortunately I don't know which version). There I had defined some aliases that no longer work in the current version. In particular, alias that uses ConEmu switches "-cur_console" and "-new_console". For example, I have an alias with which I can edit the alias file directly:
salias=vim %SCRIPT_PATH%\cmder\config\user_aliases.cmd -new_console:n
Vim crashes directly after execution:
Crash after the option argument: "-new_console:n"
Another alias is to add a path to the environment variables:
path=setx /m OWN_PATHS "%OWN_PATHS%;$*" -new_console:abn
The error:
ERROR: Access to the registry path was denied.
As I said, all the commands worked with the old CMDER version. Is there a setting that will make this work again? And if not with switches, is there a way to run commands/aliases with admin rights, without to start a new console as admin?
Thank you very much.
Checklist
- I have read the documentation and made sure what I'm looking for isn't present, or is unclear.
- I have searched for similar issues, and either this question wasn't asked before, or I didn't find any that describe my question.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the salias and path examples from the issue and compare their behavior with the older Cmder version if available. Review current alias handling for the -new_console and -cur_console switches, then document whether admin commands can run without a new elevated console and what the supported behavior is.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell, vim
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100