jesseduffield / jesseduffield/lazygit
lazygit doesn't work from a Cygwin shell prompt.
- Dominant language
- Go
- Stars
- 82.4k
- Forks
- 3k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 19
Description
### Describe the bug
`lazygit` doesn't work from a Cygwin shell prompt.
### To Reproduce
Steps to reproduce the behavior:
1. Start a Cygwin shell.
2. Attempt to execute `lazygit`.
3. Observe that it crashes.
### Expected behavior
One would hope `lazygit` would work just fine from a Cygwin prompt.
### Screenshots
```
❪Cygwin❫▶ lazygit
2025/12/09 16:28:11 An error occurred! Please create an issue at: https://github.com/jesseduffield/lazygit/issues
*fs.PathError chdir /cygdrive/c/Workspace/gameservice: The system cannot find the path specified.
/home/runner/work/lazygit/lazygit/pkg/utils/errors.go:13 (0x7ff6261aef09)
/home/runner/work/lazygit/lazygit/pkg/commands/git.go:72 (0x7ff6261aef0a)
/home/runner/work/lazygit/lazygit/pkg/gui/gui.go:323 (0x7ff626365d05)
/home/runner/work/lazygit/lazygit/pkg/gui/gui.go:864 (0x7ff62636a9ea)
/home/runner/work/lazygit/lazygit/pkg/gui/gui.go:885 (0x7ff62636aec8)
/home/runner/work/lazygit/lazygit/pkg/utils/utils.go:80 (0x7ff625f32156)
/home/runner/work/lazygit/lazygit/pkg/gui/gui.go:884 (0x7ff62636adff)
/home/runner/work/lazygit/lazygit/pkg/app/app.go:277 (0x7ff6263ce61a)
/home/runner/work/lazygit/lazygit/pkg/app/app.go:48 (0x7ff6263ce5aa)
/home/runner/work/lazygit/lazygit/pkg/app/entry_point.go:177 (0x7ff6263d0985)
/home/runner/work/lazygit/lazygit/main.go:23 (0x7ff6263d1cf8)
/opt/hostedtoolcache/go/1.25.4/x64/src/internal/runtime/atomic/types.go:194 (0x7ff625b6a2bd)
/opt/hostedtoolcache/go/1.25.4/x64/src/runtime/asm_amd64.s:1693 (0x7ff625ba6aa1)
```
### Version info:
```
❪Cygwin❫▶ lazygit --version
commit=17d03ec8cb89d4c65fd129228164562a220abefb, build date=2025-12-06T13:01:50Z, build source=binaryRelease, version=0.57.0, os=windows, arch=amd64, git version=2.51.0
❪Cygwin❫▶ git --version
git version 2.51.0
```
### Additional context
I tried running the very same `lazygit` executable from a Windows CMD prompt and it worked fine.
Contributor guide
Assessment
This issue has not been assessed yet.