-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cmder looking for user-aliases in wrong path #1039
Comments
Renaming |
Did you maybe delete or not copy in /~https://github.com/cmderdev/cmder/blob/master/vendor/user-aliases.cmd.example? |
Data is in Had deleted the example file, yes. Re-added it. Output now is:
Aliases still don't work. |
Yeah you need to stop messing with the file structure on your own, I just tested it on a fresh folder and it works fine. |
Ok, other question. Where do I put my data from the old |
After readding the example file, closing and reopening cmder it now works as expected. Why is cmder messed up when removing the example file? I'm probably not the only one who'd do that. |
It uses it to generate the content of the real file, and yes I agree that the method is sub-optimal but better than what we had before. Maybe @daxgames will look into it again and maybe have the file generated without using a dummy file. |
@jrappen I know this is closed but want to make sure things are working as designed. If you had an existing aliases file in %CMDER_ROOT%\config\aliases and copied the 1.3 release files from an extracted archive into %COMDER_ROOT% then the init.bat is supposed to update your existing aliases file to the new format. Did you copy the new release into an existing %CMDER_ROOT% folder or start with a fresh new folder with 1.3? If %CMDER_ROOT%\config\aliases does not exist when launching 1.3 the first time, from a new folder, a new default %CMDER_ROOT%\config\user-aliases.cmd is created from the seed file. |
@daxgames I had downloaded
It seems like cmder was looking in /cc @Stanzilla |
After updating to
v1.3.0
:Roughly translated:
Wrong syntax for file name, folder name or drive name. / 0 files copied. / System was unable to find the desired file.
The text was updated successfully, but these errors were encountered: