Windows
xcsh can be run on Windows using npm or Windows Subsystem for Linux (WSL).
Option 1: npm (Recommended)
Section titled “Option 1: npm (Recommended)”Install xcsh globally using npm:
npm install -g @robinmordasiewicz/f5xc-xcshThen run:
xcsh versionOption 2: WSL
Section titled “Option 2: WSL”For the best experience on Windows, use Windows Subsystem for Linux (WSL):
-
Install WSL with Ubuntu:
Terminal window wsl --install -
Open Ubuntu and follow the Script installation method:
Terminal window curl -fsSL https://robinmordasiewicz.github.io/f5xc-xcsh/install.sh | sh
PowerShell Completions
Section titled “PowerShell Completions”Enable tab completion in PowerShell:
xcsh completion powershell | Out-String | Invoke-ExpressionTo make completions permanent, add the above command to your PowerShell profile:
# Open your profile for editingnotepad $PROFILE
# Add this line:xcsh completion powershell | Out-String | Invoke-ExpressionTroubleshooting
Section titled “Troubleshooting”Command Not Found
Section titled “Command Not Found”Ensure npm’s global bin directory is in your PATH:
npm config get prefixAdd the \bin subdirectory of that path to your system PATH.
Execution Policy
Section titled “Execution Policy”If PowerShell blocks scripts, adjust the execution policy:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser