Mohammed Nasir dil-mnasir
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| font-family = BerkeleyMono Nerd Font | |
| #font-family = Iosevka Nerd Font | |
| # font-family = SFMono Nerd Font | |
| font-size = 20 | |
| theme = GruvboxDarkHard | |
| shell-integration-features = no-cursor,sudo,no-title | |
| cursor-style = block | |
| adjust-cell-height = 35% | |
| # background-opacity = 0.96 |
glenkusuma
/ install-zsh-windows-git-bash.md
Last active
November 3, 2025 14:43
— forked from fworks/install-zsh-windows-git-bash.md
Zsh / Oh-my-zsh on Windows Git Bash
DeanPDX
/ Windows 10 - Using Git Bash With TMUX.md
Last active
November 12, 2025 17:19
I tried the WSL and it isn't quite seamless enough for me. I ran in to problems when editing in VSCode and having watchers on my files (ng serve, dotnet watch run, etc.). In addition, I kept running in to problems that only manifest themselves when running in WSL. For example, this issue with doing production builds and the terser plugin has made many a developer rage-quit on using WSL. Just figuring out that it was an issue with the WSL took a lot of time.
That terser plugin issue was never resolved and I ended up having to keep a git bash window open in addition to my WSL console window so I could do production builds. To make matters worse, my npm packages were platform-dependent so I couldn't use the same project folder. So, my procedure was: commit whatever changes to test branch, push to repo, git pull on my "windows" project folder, and do a production build there