Cmder: `cd/d D:` always goes to `D:\Programs\Cmder\config\profile.d`
As I put Cmder at D:\Programs\Cmder, every time when I change directory by:
~ shell
D:
cd/d D:
cmder /single "D:"
~
It will goes to D:\Programs\Cmder\config\profile.d actually.
And I've noticed something like below (the C: goes to %HOME% is the same as Windows's Cmd):
- Given path with
/means the absolute path, it's obvious. - Without
/, it seems like it will goes to theHOMEfolder but I'm not sure.
Any explanation?
hyrious
All 3 comments
Getting same issue. Fairly new to using cli so I am not sure what to do
manizm
on 16 Mar 2017
More details I've found these days.
- Windows' Cmd will remember the last directory of the disk you've worked at, and when you
cdback to the same disk (without/), it will be there.
- Same behavior will be seen on Cmder, so we could conclude this:
Cmder's last working directory is%CMDER_ROOT%/config/profile.d, which means Cmder runs cmd.exe at this path, and then goes to the real destination, e.g. %HOME%.
If the target path's disk is the same as %CMDER_ROOT%'s, it's no problem.
So, if you want to make a change, go set some init scripts to cd to the root of this disk. ;-)
~ cmd
:: %CMDER_ROOT%configuser-profile.cmd
set "init_current_path=%cd%"
cd /d D:/
cd /d %init_current_path%
set init_current_path=
~
But it will not change cmder /single "D:"'s behavior.
*.{bat|cmd}s at %CMDER_ROOT%/config/profile.d are going to be init scripts, where we may know the reason for it becomes the last path Cmder worked at before program getting ready.
hyrious
on 17 Mar 2017
file user_aliases.cmd, add new line:
D:=cd /d D:/
DongZhe93
on 21 Sep 2020
Related issues
zsedcbm
·
3Comments
brunowego
·
3Comments
jordanrobinson
·
3Comments
emesx
·
3Comments
GlassGruber
·
3Comments
Most helpful comment
More details I've found these days.
cdback to the same disk (without/), it will be there.Cmder's last working directory is
%CMDER_ROOT%/config/profile.d, which means Cmder runs cmd.exe at this path, and then goes to the real destination, e.g. %HOME%.If the target path's disk is the same as %CMDER_ROOT%'s, it's no problem.
So, if you want to make a change, go set some init scripts to
cdto the root of this disk. ;-)~ cmd:: %CMDER_ROOT%configuser-profile.cmd
set "init_current_path=%cd%"
cd /d D:/
cd /d %init_current_path%
set init_current_path=
~
But it will not change
cmder /single "D:"'s behavior.*.{bat|cmd}s at%CMDER_ROOT%/config/profile.dare going to be init scripts, where we may know the reason for it becomes the last path Cmder worked at before program getting ready.