为何zsh脚本无法识别路径中的~（波浪号）？兼bash兼容适配问题

Hey there, let's break down this quirky behavior you're seeing and lock in a cross-shell solution that works for both your team's bash setup and your zsh preference.

Why ~ Sometimes Fails in Zsh #

The root issue boils down to how tilde expansion (converting ~ to your home directory) behaves differently across shells, especially inside double quotes:

• In bash, ~ gets reliably expanded to $HOME even when wrapped in double quotes, no matter where it sits in the string.
• In zsh, the default rules are stricter: ~ only expands to $HOME in double quotes if it’s the first character of the string. If certain zsh options are toggled, or if the script runs in a different context (like being executed as a standalone file vs sourced), it might fail to expand—hence the random "works sometimes, doesn't other times" behavior you noticed.

Cross-Shell Compatible Fix #

To eliminate this inconsistency entirely, ditch ~ in your PATH exports and use $HOME instead. It’s universally supported in both bash and zsh, and expands reliably inside double quotes every single time.

Bad (inconsistent across shells):

export PATH="~/path/to/stuff/"

Good (works everywhere, plus preserves your existing PATH):

export PATH="$HOME/path/to/stuff:$PATH"

Pro tip: Don’t forget to append :$PATH! Skip this, and you’ll overwrite your existing PATH entirely, losing access to all other system commands.

Bonus: Keeping Shared Scripts Friendly for Both Shells #

Since your team uses bash and you prefer zsh, here are a couple quick steps to avoid future headaches:

• Add a shebang at the top of shared scripts: #!/usr/bin/env bash ensures the script runs in bash even when executed from zsh, preventing zsh-specific surprises.
• Avoid zsh-only syntax (like special glob modifiers or unique aliases) in team scripts to keep them fully bash-compatible.

内容的提问来源于stack exchange，提问作者PhillyStafford