MacBook Pro（2012中款）Shell命令缺失，求开发环境配置方案

Hey Andrea, let's tackle this frustrating issue step by step—losing access to basic commands like ls is such a roadblock when you're trying to set up a dev environment. Here's how to get your 2012 MacBook Pro (High Sierra 10.13) back on track:

1. Emergency Fix: Restore Basic Command Access #

First off, those core commands aren't actually missing—your PATH environment variable is probably broken or unconfigured. macOS stores all default system commands in /usr/bin and /bin, so let's start by confirming they exist:

# Manually run ls to verify it's there
/usr/bin/ls

If that works, temporarily reset your PATH to include all standard system directories:

export PATH="/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin"

Now try ls, cd, or echo—they should work normally again.

2. Create & Configure Bash Initialization Files #

macOS doesn't automatically create .bashrc or .profile for new users, so we'll build them from scratch and link your existing optimized config:

1. Navigate to your home directory:

   cd ~
   

2. Create a .bash_profile (this is the file macOS's bash reads by default for login shells):

   /usr/bin/touch .bash_profile
   

3. Open it with nano (a built-in text editor) to set a permanent PATH and link to your .bashrc:

   nano .bash_profile
   

   Paste this content into the file:

   # Set permanent system PATH
   export PATH="/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:$PATH"
   
   # Load custom bash config from .bashrc if it exists
   if [ -f ~/.bashrc ]; then
       source ~/.bashrc
   fi
   

   Save and exit: press Ctrl+O, hit Enter, then Ctrl+X.
4. Create your .bashrc file to import your old device's config:

   /usr/bin/touch .bashrc
   

   Now copy the content from your old device's optimized .bashrc into this file (you can transfer it via USB drive, then use /usr/bin/cp to copy the file into ~/.bashrc).

3. Verify Bash Loading Behavior #

Since you're running bash 4.4.12 (not macOS's default 3.2.x), double-check that your config loads correctly:

• Run echo $BASH_VERSION to confirm your bash version.
• Restart your terminal, or run source ~/.bash_profile to load the new config immediately.
• Test a command from your old config to make sure it works now that the base PATH is set.

4. Add Missing Dev Tools (If Needed) #

If your old config relies on commands like git, node, or other dev tools, install Homebrew to easily manage them:

1. First install Xcode Command Line Tools (required for Homebrew):

   xcode-select --install
   

2. Install Homebrew:

   /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
   

   Homebrew will automatically add its directory (/usr/local/bin) to your PATH, so any tools you install with brew install [tool-name] will be available immediately.

Once you've completed these steps, your bash environment should behave like your old device's, with all core commands and your custom config working as expected.

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