When both fish and nushell are detected, the install loop could carry over previously assigned fzf_completion / fzf_key_bindings values and write a nushell source line into fish config in partial-enable flows (key bindings only or completion only).

• Root cause

  • nushell was skipped after shell-specific source variables were assigned, allowing stale values to leak into later fish update logic.

• Change

  • Reordered loop control in install so nushell is skipped immediately at loop entry, before assigning:
    • fzf_completion
    • fzf_key_bindings
  • This keeps fish/bash/zsh variable values shell-correct and avoids cross-shell contamination.

• Code snippet

  for shell in $shells; do
    [[ $shell == nushell ]] && continue
    fzf_completion="source \"$fzf_base/shell/completion.${shell}\""
    fzf_key_bindings="source \"$fzf_base/shell/key-bindings.${shell}\""
    [[ $shell == fish ]] && continue
    ...
  done