Cmder: Startup directory doesn't work

[thany]

When I've got a Cmder window open, and right-click in the tab bar to select New console, the startup directory chosen in the dialog that appears isn't respected. It always starts in my home directory (C:\Users\username) no matter what options I choose. It also doesn't matter if I do this from an elevated Cmder or not.

I've updated literally minutes ago, so everything should be up-to-date.
Cmder version 1.3.2
ConEmu version 161206
Windows 10 x64

[kibbled]

Same here on Windows 7. Also if I close the second tab it crashes Cmder but not if I close the first tab after opening a second. Running latest build 161206 64-bit stable

[ZenToad]

Same problem here. Windows 10

[Saturate]

Same issue for me

[thany]

Looks like the issue is in the software then, not in the user 🙂

[lebedev]

TL;DR: delete :d:%USERPROFILE% from Cmder task's command.

Actually, it works as intended. And by that I mean that new Cmder actually starts within specified "Startup directory for new process" and then it's working directory gets changed to whatever else.

So, in a task's command that starts cmder you can see something like -new_console:d:"%USERPROFILE%". According to -new_console's syntax, d flag is for changing working directory. Therefore for that command to not change directory just remove that switch and this issue will be fixed for you.

[thany]

I haven't added that to the command, so whatever the bug exactly is, is caused by default behaviour. Ergo, it still needs a fix and the suggestion you provide is merely a workaround.

And with all due respect, "it works as intended" in my mind reads as "it is intended wrongly" ;)

[thany]

Can I ask why this issue is closed? Has it been resolved in any way?

[lebedev]

It has been in #1504, as you can see right above your message.

[drunkwretch]

@angly-cat thx save me