| Environment | Config file location | |-------------|----------------------| | (Git for Windows) | ~/.bashrc (usually C:\Users\YourName\.bashrc ) | | WSL (Windows Subsystem for Linux) | ~/.bashrc inside the Linux distro | | MSYS2 / Cygwin | ~/.bashrc |
export PS1="\u@\h \w[\033[32m]$(parse_git_branch)[\033[00m] $ " After editing .bashrc , run:
So yes— in all of them. The trick is making sure it’s actually loaded. The Problem: Bash on Windows Doesn’t Always Read .bashrc In Git Bash, when you open the terminal, it often runs as a login shell (which reads .bash_profile ) or an interactive non‑login shell (which should read .bashrc ). But sometimes it doesn’t.
If you’ve just moved from macOS or Linux to Windows (or you’re dual-booting), one of the first things you’ll miss is your trusty .bashrc . That one file where you store aliases, custom prompts, and environment variables.
Your fingers will thank you the first time you type ll instead of ls -la . Do you use a .bashrc on Windows? Share your favorite alias in the comments.
# ~/.bashrc for Windows alias ll='ls -la' alias ..='cd ..' alias c='clear' Open current folder in File Explorer alias explore='start .' Open a file with default Windows app alias open='start ""' Git shortcuts alias gs='git status' alias ga='git add .' alias gc='git commit -m' alias gp='git push' Python on Windows (if using regular Python, not WSL) alias py='winpty python' Custom prompt (shows Git branch if in a repo) parse_git_branch() sed -e '/^[^ ]/d' -e 's/ (.*)/ (\1)/'
