Christian Klauser

Just as a heads up for the maintainers, there seem to be three PRs for this issue by now 1. https://github.com/fede1024/rust-rdkafka/pull/671 2. https://github.com/fede1024/rust-rdkafka/pull/688 3. https://github.com/fede1024/rust-rdkafka/pull/691 (this PR) (I don't care...

There is a trade off here. Nushell differentiates between "modules" and "scripts". That means a file either exports definitions (when used together with `use`) _or_ it executes code (when `source`ed)....

One more idea from the nushell discord: combine [custom completers (for a single external command decl)](https://www.nushell.sh/book/custom_completions.html) with [rest parameters](https://www.nushell.sh/book/custom_commands.html#rest-parameters) ``` def "nu-complete foo" [ctx: string, pos: int] { } def...

Note for the implementation: we need to check that we handle `some pipeline | some-clap-tool arg1` correctly. Nushell includes the `|` as a first argument. I suppose some tools might...

(@Hofer-Julian if you are itching to tackle this issue, please feel free. I won't find time in the next couple of weeks myself)

@Hofer-Julian that would be https://github.com/jj-vcs/jj/compare/main...chklauser:jj:push-rppypvvytuqv

> Auto-updating is a hard requirement imo. Shouldn't that be the responsibility of the distribution/packager? I understand that auto update is convenient for tools that are `cargo install`ed but that...

I have updated the implementation in the PR to do auto-updating. It still requires more machinery than other shells, but from the user's perspective, it's fairly transparent. I have had...

I'd say so,yes. With command-wide completion handlers, the completions are scoped to just the jj command. Question is if this changes anything about the solution as a whole. Like: if...

PR is updated. Works fine 👍 ```nushell # Performs the completion for jj def jj-completer [ spans: list # The spans that were passed to the external completer closure ]:...