Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

generate shell completion is changed in v0.71.0 #3037

Closed
daeho-ro opened this issue Dec 7, 2024 · 1 comment · Fixed by #3040
Closed

generate shell completion is changed in v0.71.0 #3037

daeho-ro opened this issue Dec 7, 2024 · 1 comment · Fixed by #3040

Comments

@daeho-ro
Copy link

daeho-ro commented Dec 7, 2024

Hello,

I have noticed that the generating shell completion is a bit weird now,

bindgen --generate-shell-completions 
error: a value is required for '--generate-shell-completions <SHELL>' but none was supplied
  [possible values: bash, elvish, fish, powershell, zsh]

For more information, try '--help'.

The option --generate-shell-completions requires shell input and so put it leads to an error

bindgen --generate-shell-completions bash
error: the following required arguments were not provided:
  <HEADER>

Usage: bindgen <FLAGS> <OPTIONS> <HEADER> -- <CLANG_ARGS>...

For more information, try '--help'.

It seems that the usage is changed and not documented on the command.

This is happen on the homebrew CI here,

Thanks,

@jbeich
Copy link

jbeich commented Dec 7, 2024

Duplicate of #2677 (comment) ? Workaround: pass a dummy header: bindgen --generate-shell-completions bash whatever

heftig added a commit to heftig/rust-bindgen that referenced this issue Dec 7, 2024
This regressed again in rust-lang#2984. Partially revert d75fe27 and
42a86e2 and restore the previous behavior.

Fixes: rust-lang#3037
Fixes: rust-lang#3039
pvdrz added a commit to heftig/rust-bindgen that referenced this issue Dec 8, 2024
pvdrz added a commit to heftig/rust-bindgen that referenced this issue Dec 8, 2024
github-merge-queue bot pushed a commit that referenced this issue Dec 8, 2024
This regressed again in #2984. Partially revert d75fe27 and
42a86e2 and restore the previous behavior.

Fixes: #3037
Fixes: #3039
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants