nom-build: zsh bridge does not work

[Atemu]

Current Behavior

Attempting to complete nom-build which ships a zsh-completion in CARAPACE_BRIDGES=zsh nu does not work: NO RECORDS FOUND.

Perhaps this is to do with the completion being equal to some other completion?

Expected Behavior

It should do zsh nix-build completions for nom-build.

Steps To Reproduce

1. In an env where zsh and nix-output-monitor are installed
2. Run CARAPACE_BRIDGES=zsh nu
3. Try to complete nom-build <TAB>

Version

1.0.2

OS

• Linux
• OSX
• Windows

Shell

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

Anything else?

Nom basically declares itself as an alias. That may be the reason?

Related to this: Should carapace attempt to use its own completions for the command aliased by the bridge or should it use the bridge's aliased command via the bridge too?

Least surprise would probably be to use the aliased command completion via the bridge as command aliases should be handled by carapace itself for native completions.

[rsteube]

Nom basically declares itself as an alias. That may be the reason?

Yeah possibly. Haven't gone too deeply into that edge case.

Apart from that carapace uses a custom config at ~/.config/carapace/bridge/zsh/.zshrc, so if the nom-build completion is registerd in ~/.zshrc that needs to be repeated there.

There's a custom completer for nix-build in carapace. Might be easier to just bridge completions for that one with a spec:

# yaml-language-server: $schema=https://carapace.sh/schemas/command.json
name: nom-build
parsing: disabled
completion:
  positionalany: ["$carapace.bridge.CarapaceBin([nix-build])"]

[Atemu]

Oh so that's what the carapace bridge is for; it struck me as kind of odd.

[rsteube]

Sourcing the users .zshrc can be very slow (depending on whate users put in there) and have some nasty side effects.
So I'm kinda forced to use a seperate one.
System wide registered completions should work though.

[Atemu]

Ah, sorry I forgot to reply to that part; this is indeed a system-wide completion. It's not at the usual path as I'm on NixOS but the default system zsh is made to discover it just fine.

[blindFS]

@rsteube For me, CARAPACE_BRIDGES=zsh doesn't work at all, however anything defined in ~/.config/carapace/bridges.yaml is working perfectly. I wonder how to make zsh the default bridge for all commands that lack a default completer?

my ~/.config/carapace/bridge/zsh/.zshrc:

fpath=(/run/current-system/sw/share/zsh/site-functions $fpath)
autoload -U compinit && compinit

[blindFS]

CARAPACE_BRIDGES do make differences:

but the completion just not working for nushell.

[rsteube]

The amount shown in --list does not use your fpath in ~/.config/carapace/bridge/zsh/.zshrc.
See https://github.com/carapace-sh/carapace-bridge/blob/master/pkg/bridges/zsh.go#L23

Is this just related to a specific completer, or a general issue with the zsh bridge?
Might just need to ensure ~/.config/carapace/bridge/zsh/.zshrc is used so that completion functions from the updated fpath are registered.

[blindFS]

@rsteube All commands specified in ~/.config/carapace/bridges.yaml works as expected, so I think fpath is loaded correctly.
The only issue for me is that, the list of commands that I want to bridge to zsh can be long, and I really want the CARAPACE_BRIDGES env var to work in a sense that all commands missing the completion info fallback to the zsh bridge, or maybe it's designed work in other ways?

Just curious about how to specify a default bridge without manually adding stuffs to bridges.yaml.

[rsteube]

CARAPACE_BRIDGES does exactly that.
If none is registered in carapace it falls back to the bridged completion.

[blindFS]

The behavior of an empty bridges.yaml:

while with atuin: zsh in it:

and with a non-empty bridges.yaml that doesn't contain atuin: