-
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
Git & env related error messages #2220
Comments
Download Cmder Mini again and extract it. An incorrect binary was loaded and has since been replaced. |
I just downloaded it. The version is 1.3.13.967. I tried again, but the errors remain. I don't think this has been corrected. I am trying with previous versions. With versions 1.3.11/10/8/7 the git error is gone and the env related error remains. Version 1.3.6.678 just won't install/start (it shows another error related with an unexpected \vendor\lib\lib_base""). Versions 1.3.5/4/3/2/1 give me this message: "Found old git version in "C:", but not using..." I hope this helps. |
@Starbuck1991 the only error is: The other output is normal. Are you certain I get the 'normal' output the only FIRST time then I get the prompt. Launches after the first I just get the prompt and do not |
@daxgames yes, I'm certain this is the latest version. As I said, it seems to me that the git related error has been introduced with version 1.3.12, as versions 1.3.11/10/8/7 just output the unrecognized "env" command error. And yes, those messages happen every time I run Cmder, but only at the start, then the program runs normally until I close it and I run it again. I've created a batch file that runs at the start and just clears the screen to get rid of those error messages (I know, why bother, but I'm just that kind of person), and it seems that the program runs OK after all, but I feel that I shouldn't be receiving those errors, and something may be wrong somewhere inside the code. I just feel I'm not supposed to get any errors at all, do I? |
@Starbuck1991 I see part of the issue now. You do not have permissions to write files to the config folder when launching cmder. If those files cannot be written then cmder will try every time. This is just one of the reasons it is not recommended that cmder not be put Move cmder folder to your home folder and try again. |
@daxgames I took this in consideration when trying the program for the first time, that's why I checked all the versions in my downloads folder, located in a D drive. Anyhow, if I execute the program as admin, I should be able to run it from te Program files folder, isn't it? (but not the case). |
We do not recommend putting the cmder folder in |
It's already sitting in my D drive, no admin rights required, @daxgames. In fact, just for the sake of it, I just downloaded yet again the latest version, and tested it in a different drive (Z). This time I recorded the screen, and you'll see clearly that the issue is not related to the path: I hope this helps to clarify the issue. |
After further investigation, I edited the init.bat file and removed the git related part, as I don't need Git:
Problem solved. Still, something must be wrong with this part of the batch file... |
@Starbuck1991 Thanks for the video. It cleared things up and you are right it is not related to the path. I misunderstood your original post and thought you were getting this every time you started:
Which would have been path related. I did not understand that what you were getting everytime was:
I can't reproduce it though so it will be hard for me to code a fix. |
That's OK, no worries, this thread might help another user with the same specific problem, and provide them with a workable solution if they do not need git, albeit not an ideal one. |
@Starbuck1991 could you put back the old init.bat change lines 237-244 below:
To:
And let me know if it helps? |
Try this new build and let me know, |
I've run two tests. The first one with the init.bat file from the previous version. Your edit makes te env error go away, but the git error remains. Your new init.bat file also makes the env error dissappear, but keeps the git error and introduces a new one:
Something about "\vendor\bin" not being expected at this time. |
@Starbuck1991 I still cannot reproduce this or the new error you reported even on the new build. Does the following match your file? Line 288 in 0cf1c5e
If not you have an old file. Did you try downloading the new build and use it as a new install launching it multiple times? |
@daxgames I'm using the new build. As with the previous version, for me the cure is to delete the git part in the init.bat file. I think that something must be wrong with my system related to the git installation. for some reason, %GIT_INSTALL_ROOT% seems to point to C:\Windows. Anyhow, obviously there is no git installation at this path, so I think git detection should fail at this point and skip to the next section. |
@Starbuck1991 can you edit the task that is launching cmder and add |
@Starbuck1991 there are also |
@Starbuck1991 ??? |
Hi, @daxgames, been very busy, excuse me for the delay. this is the
I see nothing wrong except for the last part, because as I said, |
And this is the output of using /d /v :
|
@Starbuck1991 why is there a git.exe in c:\windows? Rename it and see what happens. |
I don't know what the file was doing there. I swear I checked it, and saw no git.exe in c:\windows, but it was there indeed. I have deleted it, and the errors are gone. |
Awesome! |
Purpose of the issue
Version Information
Mini 1.3.13.967
Windows 10 Pro 1903
Description of the issue
Every time I run Cmder for the first time I get this (sorry, it's in Spanish):
Generating clink initial settings in "C:\Program Files\cmder\config\settings"
1 archivo(s) copiado(s).
Additional *.lua files in "C:\Program Files\cmder\config" are loaded on startup.
error launching git: El sistema no puede encontrar la ruta especificada.
"env" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
Creating initial user_aliases store in "C:\Program Files\cmder\config\user_aliases.cmd"...
1 archivo(s) copiado(s).
Creating user startup file: "C:\Program Files\cmder\config\user_profile.cmd"
1 archivo(s) copiado(s).
The installer complains about not finding the git path (I've got no git, and I don't want it, that's why I choose the Mini version), and about not recognizing the "env" command.
Then, every time I run cmder, I get the same error messages:
error launching git: El sistema no puede encontrar la ruta especificada.
"env" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
How can I make those errors go away?
The text was updated successfully, but these errors were encountered: