-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
CMDER_START should always be set to USERPROFILE unless explicitly set through /START parameter #772
Comments
cmder is also registered as |
Whatever, adding it also didn't make cmder start up in the directory I rightclicked. |
I haven't made these changes yet, but it should fix most issues regarding |
Ok, I think it's ok not to have /START in the context menu integration, but I think that the path argument is ignored in https://github.com/cmderdev/cmder/blob/development/launcher/src/CmderLauncher.cpp#L155 So in the moment it looks like the right click integration is broken? At least it doesn't work on my computer :-( |
The problem with cmder_here stems from the fact that the tasks do not use CMDER_START as an initial directory to work with. Which is part of this issue. |
What should the outcome be here?
It seems for Unfortunately, the IMO:
IMO this could be done by letting |
tried to make #772 (comment) happen in #798 |
CMDER_START should always be set as a result of either: 1. The user passes a directory to cmder.exe using `/START $DIR` - or - 2. Sets CMDER_START as a default environment variable. Fixes #772
@JanSchulz See #803 also. |
CMDER_START should always be set as a result of either: 1. The user passes a directory to cmder.exe using `/START $DIR` - or - 2. Sets CMDER_START as a default environment variable. Fixes cmderdev#772
The text was updated successfully, but these errors were encountered: