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

No color scheme in tabs opened as Administrator #94

Closed
gsbabil opened this issue Dec 23, 2013 · 6 comments
Closed

No color scheme in tabs opened as Administrator #94

gsbabil opened this issue Dec 23, 2013 · 6 comments
Assignees
Milestone

Comments

@gsbabil
Copy link

gsbabil commented Dec 23, 2013

  • Cmder version: 1.1.2 (mini)
  • OS: Windows 8 64bit

Color scheme doesn't apply if Cmder is run as current user and a new tab is opened with Run as Administrator. The error message says - The system cannot find the path specified.

If Cmder.exe is originally run as administrator and then a new tab is opened within this session, everything works. But obviously a regular user session can not be opened anymore (everything runs as administrator).

@MartiUK
Copy link
Member

MartiUK commented Jan 9, 2014

Hi @gsbabil, does this still affect you on version 1.1.3?

@gsbabil
Copy link
Author

gsbabil commented Jan 9, 2014

@MartiUK Yes, I just tested and the issues is still here with version 1.1.3.

@ghost ghost assigned MartiUK Jan 9, 2014
@MartiUK
Copy link
Member

MartiUK commented Jan 9, 2014

@gsbabil May be a Win 8 specific problem since it works just fine on Win 7 64bit, will look at it tonight.

@Woodham
Copy link

Woodham commented Feb 25, 2014

I had this same problem on Windows 7 64bit. I've solved it by manually creating the "CMDER_ROOT" environment variable that points to where I put cmder ("C:\cmder")

@gsbabil
Copy link
Author

gsbabil commented Feb 25, 2014

@Woodham thanks a lot. I just tested it. CMDER_ROOT environmental variable solves the problem.

@MartiUK MartiUK closed this as completed Feb 26, 2014
@glucas
Copy link
Contributor

glucas commented Mar 13, 2014

While the workaround is easy enough, it would be nice if Cmder handled this 'out of the box'.
I've just gotten this working by using paths relative to %ConEmuDir% in some places instead of CMDER_ROOT. I'll see if I can clean it up and submit a pull request.

glucas added a commit to glucas/cmder that referenced this issue Mar 13, 2014
When starting a shell as Administrator, the CMDER_ROOT variable is
not propagated from the parent (non-Admin) environment.
Fix this by using paths relative to %ConEmuDir%.

Fixes issue cmderdev#94.
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

4 participants