How to change the default shell to Nushell (installed using brew)?

[ugreg]

I have a question similar to this one about fish. Is there a configuration to set Nushell as the default shell?

I see even in this community configuration tool it is not listed as a supported option, so maybe Ghostty does not support this shell yet?

Relevant other discussions:

• Add Nushell as a "Shell integration style" option

[jcollie]

Similar to the other discussion, just add the following to your config:

command = /usr/bin/nu

[ugreg]

@jcollie thanks for the quick reply! Updated my title, in my case since I am using homebrew, I had to add this (future reader versions be different mine is 0.101.0_1/ right now) command = /opt/homebrew/Cellar/nushell/0.101.0_1/bin/nu to my Ghostty config and it worked.

[ugreg]

Also @jcollie this is not supported shell-integration = nu is there plan to add more native support for Nushell in the future, rather than having the user point to the bin?

[jcollie]

Nu already has shell integration built in, so it's not necessary for Ghostty to add it's own. Set shell-integration = none.

[EdmundsEcho]

Very useful information. Being new to nushell and ghostty this information fills in some important FYIs. Thank you.

[angelplusultra]

Can't get Nushell to work properly in Ghostty. If I set the command option to /opt/homebrew/bin/nu and restart Ghostty, it will open in Nushell but a lot of my binaries are missing now and I'm getting a weird error at startup. it is basically the same error as this. The solution provided is for Fish though, does anyone know how to fix this with Nushell?

[EdmundsEcho]

It sounds like your PATH is not being set properly. run $env.PATH to see. My understanding of the "trick" to get nushell to work with ghostty is a couple of things:

1. make sure you know what file is being used to configure ghostty (it could be in ~/Library or better XDG location).
2. in your ghostty config file include the following command = /Users/edmund/.cargo/bin/nu - note how I did not use $HOME.
3. in your nushell env file be sure to set your path in a way that replicates whatever shell you were using before (in my case I was using fish shell).

Here is a snippet for (3). I'm not clear if all of what I'm providing you is required, but what I have now is working.

use std/util "path add"

# ---------------------------------------------------------
# Specifies how environment variables are:
# - converted from a string to a value on Nushell startup (from_string)
# - converted from a value back to a string when running external commands (to_string)
# Note: The conversions happen *after* config.nu is loaded
$env.ENV_CONVERSIONS = $env.ENV_CONVERSIONS | merge {
    "XDG_DATA_DIRS": {
        from_string: {|s| $s | split row (char esep) | path expand --no-symlink }
        to_string: {|v| $v | path expand --no-symlink | str join (char esep) }
    }
}

# ---------------------------------------------------------
# Directories to search for scripts when calling source or use
# The default for this is $nu.default-config-dir/scripts
$env.NU_LIB_DIRS = [
    ($nu.default-config-dir | path join 'scripts') # add <nushell-config-dir>/scripts
    ($nu.data-dir | path join 'completions') # default home for nushell completions
]

# Directories to search for plugin binaries when calling register
# The default for this is $nu.default-config-dir/plugins
$env.NU_PLUGIN_DIRS = [
    ($nu.default-config-dir | path join 'plugins') # add <nushell-config-dir>/plugins
]

# ---------------------------------------------------------
# Paths
path add $"($env.HOME)/.local/bin"
path add $"($env.HOME)/.krew/bin"
path add $"($env.HOME)/.yarn/bin"
...etc