Skip to content

Latest commit

 

History

History
80 lines (51 loc) · 1.97 KB

File metadata and controls

80 lines (51 loc) · 1.97 KB

Git Bash / MINGW64 Compatibility

Problem

When using Git Bash, MINGW64, or other bash terminals, you get:

$ pxp
bash: pxp: command not found

Cause

Pxp uses .bat (batch) files which only work in Windows Command Prompt and PowerShell. Bash terminals on Windows don't recognize .bat files as executable commands.

Solutions

Solution 1: Use PowerShell or CMD (Recommended)

Simply switch to PowerShell or Command Prompt to run Pxp:

  • PowerShell: Press Win + X and select "Windows PowerShell" or "Terminal"
  • CMD: Press Win + R, type cmd, and press Enter

Then run your pxp commands normally.

Solution 2: Create a Bash Alias

Add this to your ~/.bashrc or ~/.bash_profile:

# Pxp alias for Git Bash
pxp() {
    powershell.exe -ExecutionPolicy Bypass -File "C:/Program Files (x86)/Pxp/pxp.ps1" "$@"
}

Note: Adjust the path if Pxp is installed elsewhere. Use forward slashes (/) instead of backslashes.

After adding the alias:

  1. Restart your bash terminal, or
  2. Run: source ~/.bashrc

Now you can use pxp commands in Git Bash.

Solution 3: Run via PowerShell Command

You can run Pxp directly from bash using PowerShell:

powershell.exe -ExecutionPolicy Bypass -File "C:/Program Files (x86)/Pxp/pxp.ps1" list

Solution 4: Add PowerShell Function to PATH

Create a bash function wrapper. Add to ~/.bashrc:

export PXP_HOME="/c/Program Files (x86)/Pxp"
alias pxp='powershell.exe -NoProfile -ExecutionPolicy Bypass -File "$PXP_HOME/pxp.ps1"'

Important Notes for Bash Users

  • Pxp is designed for Windows environments (PowerShell/CMD)
  • It manages XAMPP which is a Windows application
  • For the best experience, use PowerShell or CMD when working with Pxp

Testing Your Setup

After configuring, test with:

pxp --version

Related Resources