Nushell support

[ylorn]

Describe the feature

Native nushell support — iris init nu, a real nu adapter, the whole thing.

Right now IRIS only does bash/zsh/fish. My login shell is nu (/opt/homebrew/bin/nu), and core.shell rejects anything outside bash|zsh|fish. Workaround is launching iris with -s fish/-s zsh, but then you're not actually in nu anymore (different syntax, history, completions). Not really usable as a daily driver if nu is your shell.

It should be implemented because

A bunch of people already live in nushell full-time. Without a nu adapter, iris just isn't an option unless you bounce into another shell, which kinda defeats the point.

Additional context

• Nushell: https://github.com/nushell/nushell
• Looks like the shell adapters live under integration/shell (Bash/Zsh/Fish). Nu would need the same kind of thing: spawn nu in the PTY, wire cwd/cmd start-stop hooks, and whatever line-buffer sync makes sense for nu's reedline.
• History side: nu can use sqlite history ($env.config.history.file_format = "sqlite"), so the history reader probably needs more than the plain text parsers used for bash/zsh/fish.

Happy to test builds if useful. Not planning to implement it myself though.

Would you like to work on this issue?

No

[versenilvis]

I will work on it, because I don't use nushell and have to install and use it right now, it's great if you can share me your config, I can setup an environment exactly the same as normal users and you (tho never require)

[ylorn]

sure — here's a minimal slice of my nu setup (the bits that actually matter for an adapter). stripped out personal aliases, colors, local paths, etc.

env.nu:

# env.nu
$env.XDG_CACHE_HOME = $env.XDG_CACHE_HOME? | default ($nu.home-dir | path join '.cache')
$env.XDG_CONFIG_HOME = $env.XDG_CONFIG_HOME? | default ($nu.home-dir | path join '.config')
$env.XDG_DATA_HOME = $env.XDG_DATA_HOME? | default ($nu.home-dir | path join '.local')
$env.EDITOR = 'hx'

config.nu (interactive bits):

# config.nu
$env.config.use_kitty_protocol = true
$env.config.buffer_editor = "hx"
$env.config.highlight_resolved_externals = true
$env.config.show_banner = false
$env.config.edit_mode = "vi"
$env.config.cursor_shape.vi_insert = "blink_line"
$env.config.cursor_shape.vi_normal = "block"

# history is sqlite, not plain text
$env.config.history.file_format = "sqlite"
$env.config.history.max_size = 5_000_000
$env.config.history.isolation = true
$env.config.history.ignore_space_prefixed = true

$env.config.keybindings ++= [
    { name: delete_one_word_backward, modifier: alt, keycode: backspace, mode: [emacs vi_insert], event: { edit: backspaceword } }
    { name: move_one_word_forward,    modifier: alt, keycode: char_f,    mode: [emacs vi_insert], event: { until: [{ send: historyhintwordcomplete }, { edit: movewordright }] } }
    { name: move_one_word_backward,   modifier: alt, keycode: char_b,    mode: [emacs vi_insert], event: { edit: movewordleft } }
]

$env.config.abbreviations = {
    gs: "git status"
    gp: "git push"
    gpl: "git pull"
    gc: "git commit"
}

# generate vendor autoloads once (not every start)
let vendor_dir = $nu.vendor-autoload-dirs | last
mkdir $vendor_dir

let tools = [
    { name: atuin,    cmd: { atuin init nu } }
    { name: carapace, cmd: { $env.CARAPACE_BRIDGES = 'zsh,fish,bash,inshellisense'; carapace _carapace nushell } }
    { name: starship, cmd: { starship init nu } }
    { name: zoxide,   cmd: { zoxide init nushell } }
]

for tool in $tools {
    let out = $vendor_dir | path join $"($tool.name).nu"
    if not ($out | path exists) and ((which $tool.name | length) > 0) {
        do $tool.cmd | save -f $out
    }
}

notes that might matter for iris:

• login shell is nu on macOS homebrew (/opt/homebrew/bin/nu)
• history is sqlite (history.sqlite3 under the config dir), not ~/.zsh_history-style text
• vi mode + kitty keyboard protocol on
• also run atuin / carapace / starship / zoxide via nu vendor autoload (so keybind overlap with atuin is a real thing here too, same as the bash/zsh/fish warning)

lmk if you want me to try a build

[versenilvis]

well, I'm struggling with nushell, I still can't find a way to make it work properly, I think you have to wait for a short time, now I need to fix other things