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

Revert "Set CMDER_START to homeprofile" #866

Merged
merged 1 commit into from
Mar 10, 2016

Conversation

jankatins
Copy link
Contributor

This PR is more or less to have a easier way to discuss the issue...

This reverts commit 728e83a.

The problem with always setting CMDER_START is that this makes the -new_console:d:%USERPROFILE% in the conemu task definitions unnecessary, as this is now always overwritten as CMDER_START is set. This also means that a very visible conemu UI for setting the startup dir does not work anymore (try opening a cmder windows when the default task has a -new_console:d:c:\temp) which might leave the user puzzled.

So: what is the use case for always setting the variable and if that's important: why not set it in the startup scripts after they have checked where to start up?

This reverts commit 728e83a.

The problem with *always* setting CMDER_START is that this makes the
`-new_console:d:%USERPROFILE%` in the conemu task definitions unnecessary, as
this is now always overwritten as CMDER_START is set. This also means that a
very visible conemu UI for setting the startup dir does not work anymore which
might leave the user puzzled why.
MartiUK added a commit that referenced this pull request Mar 10, 2016
Revert "Set CMDER_START to homeprofile"
@MartiUK MartiUK merged commit 7d21970 into cmderdev:development Mar 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants