设置Spacemacs为默认程序遇错误-9499的问题求助

Hey there! Let's break down what's going on here and get this fixed for you.

Root Cause #

Yes, your hunch is spot-on — this problem directly ties to the Emacs alias in your Applications folder instead of a full, proper .app package. Here's why:

• macOS requires a complete application bundle (.app) to set it as the default handler for file types, especially non-native ones like .fs and .fsx. Aliases (shortcuts) don't count as valid "apps" for this system-level association.
• .java files work because macOS has existing system-level associations for Java-related files that play nicer with alias-linked apps, or the brew setup handled that file type's config differently.

Step-by-Step Fixes #

1. Clean Up the Old Emacs Alias & Installation #

First, let's remove the problematic alias and old Emacs setup:

• Open Terminal and run:

  brew uninstall emacs
  

• Head to your Applications folder and delete the Emacs alias (it'll look like a file with an arrow overlay).

2. Install a Proper Emacs.app Bundle via Brew Cask #

Brew's old linkapps feature is deprecated, so we'll use the official cask install to get a full Emacs application:

• Run this in Terminal to install the GUI Emacs bundle:

  brew install --cask emacs
  

Once this finishes, you'll see a proper Emacs.app in your Applications folder (no arrow overlay — it's a full app package).

3. Reconnect Spacemacs (If Needed) #

You shouldn't need to do much here — Spacemacs will automatically detect the new Emacs.app installation since it's in the standard Applications path. If you run into any issues launching Spacemacs, double-check that your shell's emacs command points to the new cask install (run which emacs to verify; it should point to /Applications/Emacs.app/Contents/MacOS/Emacs).

4. Set Emacs as Default for .fs/.fsx Files #

Now let's fix the file association:

• Right-click any .fsx or .fs file and select Get Info.
• In the "Open with" section, click the dropdown menu and select the new Emacs.app from your Applications folder.
• Click Change All — this will apply the setting to all files of that type, and you shouldn't see the -9499 error anymore.

Bonus: Fix Corrupted File Associations (If Issues Persist) #

If you still run into problems, reset macOS's LaunchServices database to fix any broken file association data:

• Run this command in Terminal:

  /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user
  

• Restart your Mac, then try setting the default app again.

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