Cmder v1.3.13 init script fails. #2218
Comments
|
@m-ahmadi the first time one time output looks normal to me. Can't explain the lack of git prompt though. I'll look at it and will let you know. |
|
@m-ahmadi Works for me.
Output of |
|
@daxgames |
My global git config: |
|
Git config should not matter. Cannot verify right now but will do later. |
Thats fine |
|
Do the other shells work. Bash and powershell |
I guess so. (not sure if this'll suffice)
|
|
I wasnt asking tou to switch just a question. Like o said i will lookblater |
|
Running powershell from bash is probably not a good idea. |
Yes, both of them are working.
|
|
@m-ahmadi terminal app are you using? Does not look like you arr using FWIW I added your git settings to my
|
Hmm, don't know what's going on, I just re downloaded the cmder.7z file and repeated the process again, still the same thing. (also tried putting the extracted folder at a different path) I guess it has to do with the environment, is there any other config or setting you want me to provide? What Windows are you on? I'm on Win7 Ultimate SP1 (I feel like it's related to that). These are the system & user path variables: |
|
@m-ahmadi I'm on Windows 10. I cant think of anything else. |
|
I am having exactly the same problem when doing cmder.exe I followed the documentation, set the system variables and path but I am getting the same error as @m-ahmadi in his first post. |
|
@ErnestoPena as i said earlier the first time one time output looks normal. Does the git repo status in the prompt work if you chnge into a git repo. |
|
Exact same thing here with 1.3.13 on Windows 7 SP1. I redownloaded 1.3.12 and the issue is gone: |
|
I cant test this on Windows 7 since I don't have Windows 7. Backup 1.3.13 If that does not fix it put the old file back and do the same for |
This didn't change the behavior.
After reverting the previous change, I used |
Same thing here.
Same thing here. Seems to be fixed. |
1.3.13 /d /vLog |
|
@m-ahmadi I forgot to ask but could you do it again with the 1.3.12 init.bat? |
1.3.12 /d /vLog |
|
@m-ahmadi Did you copy the 1.3.12 init.bat into 1.3.13 cmder or did you use a complete 1.3.12 install? It looks like a complete 1.3.12 install based on the git version being reported in the debug output. I need you to copy the 1.3.12 init.bat into 1.3.13 cmder and post the debug output. |
No that was a complete 1.3.12 install. 1.3.13 /d /v with
|
Merged
|
Try this new build and let me know, |
|
No, seems just like the 1.3.13 version. first time opening:
other shells:
|
|
@m-ahmadi Are you running all tabs as admin? Does it work as a normal user? Looks like powershell is not working either? |
|
I did get an error on 1.3.13 too on my first launch with my previous config. Error logRunning Git for Windows one time Post Install.... "running post-install" mkdir: cannot create directory ‘/dev/shm’: Read-only file systemCreating /dev/shm directory failed. mkdir: cannot create directory ‘/dev/mqueue’: Read-only file system Creating /dev/mqueue directory failed. ln: failed to create symbolic link '/dev/stdin': Read-only file system |
|
@Makazzz so you got the standard normal first time stuff plus The first time then redownloaded new zip file as I requested others to do and now cmder opens after the first launch with no output other than the prompt appearing? Just wanting to clarify I understand. |
|
@daxgames Ok so now I did a download with a new zip from 1.3.13 and a new fresh install without any previous config and this is my error in first launch: Error log (Windows 10, on my desktop)Generating clink initial settings in "C:\Users\USERNAME\Desktop\cmder\config\settings"1 file(s) copied. Additional *.lua files in "C:\Users\USERNAME\Desktop\cmder\config" are loaded on startup. 1 file(s) copied. Running Git for Windows one time Post Install.... Creating /dev/shm directory failed. mkdir: cannot create directory ‘/dev/mqueue’: Read-only file system Creating /dev/mqueue directory failed. ln: failed to create symbolic link '/dev/stdin': Read-only file system |
|
@Makazzz That is all 100% normal for a first launch. |
|
I am now doing a new fresh install on my usb key exfat just in case |
|
@daxgames New install like my first log (USB) but fresh install. Error log (Windows 10, on my USB key ExFat)Generating clink initial settings in "G:\PortableApps\cmder3\config\settings" 1 file(s) copied. Additional *.lua files in "G:\PortableApps\cmder3\config" are loaded on startup. Creating initial user_aliases store in "G:\PortableApps\cmder3\config\user_aliases.cmd"... 1 file(s) copied. Running Git for Windows one time Post Install.... "running post-install" mkdir: cannot create directory ‘/dev/shm’: Read-only file systemCreating /dev/shm directory failed. mkdir: cannot create directory ‘/dev/mqueue’: Read-only file system Creating /dev/mqueue directory failed. ln: failed to create symbolic link '/dev/stdin': Read-only file system |
I tried both, no differences, neither of them work.
Yes, it's not working. |
|
I'm having exactly the same issue after installing Cmder To reproduce it, I've even created a Windows 7 Enterprise SP1 VM on Azure, and fount that it also has the same issue! |
|
@m-ahmadi @cateyes99 Try this Works for me on Windows 7 Enterprise. |
|
I created a Win7 eval vm and found the |
|
@daxgames |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Purpose of the issue
Version Information
Cmder version: 1.3.13
ConEmu version: 191012
Windows 7 Ultimate Service Pack 1
Description of the issue
screenshot of first time opening:
text of first time opening:
and as the result, git repo information isnt't showing and there's no color:
The text was updated successfully, but these errors were encountered: