You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating a new console/tab defaults to the directory where the Cmder is started, NOT to desired directory set in Startup directory for new process:
Example:
Start Cmder in C:\Custom-Dir
Then create a new process/tab
Set the startup dir to C:\Another-Dir
New tab opens in C:\Custom-Dir which is the first Cmder startup directory, where it should be in C:\Another-Dir or whatever is set in the new console creation
_I don't know if this is Cmder bug, or maybe i just broke something that cause this._ Found that this is not getting through #L115.
--causing the initialization scripts to fail (not moving to the wanted location).
Anyway, if anyone else having this said issue, here's how I fix it:
Here's my quick fix:
Comment out these lines in %CMDER_ROOT%\vendor\init.bat with ::
Example:
C:\Custom-Dir
C:\Another-Dir
New tab opens in
C:\Custom-Dir
which is the first Cmder startup directory, where it should be inC:\Another-Dir
or whatever is set in the new console creation_I don't know if this is Cmder bug, or maybe i just broke something that cause this._Found that this is not getting through #L115.
--causing the initialization scripts to fail (not moving to the wanted location).
Anyway, if anyone else having this said issue, here's how I fix it:Here's my quick fix:
%CMDER_ROOT%\vendor\init.bat
with::
{cmd}
in (Settings
>Startup
>Tasks
) toUpdate: Also for Powershell
%CMDER_ROOT%\vendor\profile.ps1
with#
if (Test-Path Env:\CMDER_START) { Set-Location -Path $Env:CMDER_START } elseif ($Env:CMDER_ROOT -and $Env:CMDER_ROOT.StartsWith($pwd)) { Set-Location -Path $Env:USERPROFILE }
{Powershell}
in (Settings
>Startup
>Tasks
) toThe text was updated successfully, but these errors were encountered: