carapace creates a new ~/.config/carapace in every directory the nushell open in

[mwmcode]

Current Behavior

carapace creates ~/.config/carapace in every directory the terminal starts from. [screen recording below]

Expected Behavior

It should only create carapace/ in the actual home directory (~/.config/carapace)

Steps To Reproduce

1. configure the terminal to open new windows/tabs/panes to the current working directory
2. cd ~/Desktop
3. open a new tab or pane (will open to ~/Desktop per config in step 1)
4. ls -la will show a newly created ~ folder , which contains .config/carapase/[overlays,specs]...

Demo:

carapace-issue.mov

Version

carapace-bin 1.1.1

OS

• Darwin
• Linux
• Termux
• Windows

Shell

• Bash
• Cmd
• Elvish
• Fish
• Nushell
• Oil
• Powershell
• Xonsh
• Zsh

Anything else?

env.nu

$env.CARAPACE_BRIDGES = 'zsh,fish,bash,inshellisense' # optional

config.nu

# carapace
mkdir ~/.cache/carapace
carapace _carapace nushell | save --force ~/.cache/carapace/init.nu
source ~/.cache/carapace/init.nu

Polar

[ZerdoX-x]

remove mkdir and carapace _carapace nushell lines from your config.nu

[ZerdoX-x]

I agree docs should separate config lines from one time commands

[mwmcode]

like this carapace-sh/carapace-bin#2674 ?

[rsteube]

Not sure yet what is going wrong here.
I would have expected some issues on windows as the documentation is currently pretty focussed on unix/darwin with ~ (homedir expansion).

On darwin this should work though.

---

About the instructions:

## ~/.config/nushell/env.nu
$env.CARAPACE_BRIDGES = 'zsh,fish,bash,inshellisense' # optional
mkdir ~/.cache/carapace
carapace _carapace nushell | save --force ~/.cache/carapace/init.nu

This is indeed meant to run each time to adapt to any changes between carapace versions.
(just seeing the mkdir is missing -p but seems that's not an issue)

#~/.config/nushell/config.nu
source ~/.cache/carapace/init.nu 

Nushell has a compile behaviour where the file must already exist to be sourced.
Hence the trick above with env.nu (we adopted this from starship).

---

I'd assume the ~ homedir expansion isn't working somewhere.
Are you using XDG environment variables?

[mwmcode]

Thanks for the suggestion. It was XDG_CONFIG_HOME being misconfigured 🤦‍♂️.