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
The following two files are created "out-of-place" (meaning: outside the "cmder" working environment):
.bash_history gets created in %USERPROFILE% (i.e. C:\Users\username).
winscp.rnd is created in %APPDATA% (i.e. C:\Users\username\AppData\Roaming)**
**Note: I do NOT have WinSCP installed. Deleting the file and starting Cmder creates it anew, so it clearly originates from there.
I think especially .bash_history should be stored %CMDER_ROOT%\config.bash_history ... as .history (for cmd.exe) is already stored there (apart from it being insanely handy to have your commandline history at hand when Cmder is being run off a USB thumb-drive).
The text was updated successfully, but these errors were encountered:
Hint: You're adding "--nolog" in between "--quiet" and "--profile" to disable that log-file (totally needless).
Note: You may have to redo the edits in case a future CMDER update overwrites the files without these changes being incorporated.
Oh, and since I removed "PuTTY" from my path "winscp.rnd" also disappeared (deleted and didn't come back). No idea why it happened, couldn't find a reason after auditing all the scripts to do the changes I documented above.
ghost
changed the title
.bash_history and winscp.rnd are not in Cmder's directories
[Solved myself] .bash_history and winscp.rnd are not in Cmder's directories
Jul 25, 2016
The following two files are created "out-of-place" (meaning: outside the "cmder" working environment):
.bash_history gets created in %USERPROFILE% (i.e. C:\Users\username).
winscp.rnd is created in %APPDATA% (i.e. C:\Users\username\AppData\Roaming)**
**Note: I do NOT have WinSCP installed. Deleting the file and starting Cmder creates it anew, so it clearly originates from there.
I think especially .bash_history should be stored %CMDER_ROOT%\config.bash_history ... as .history (for cmd.exe) is already stored there (apart from it being insanely handy to have your commandline history at hand when Cmder is being run off a USB thumb-drive).
The text was updated successfully, but these errors were encountered: