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
Deprecated commands used in completions, #8709
Comments
@Amorymeltzer Was this fixed by #8710? |
@MikeMcQuaid #8710 took care of it for bash — at least, I haven't run into anything — but AFAICT zsh and fish will still have some issues. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Bug report
Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.
brew update
and can still reproduce the problem?brew doctor
, fixed all issues and can still reproduce the problem?brew config
andbrew doctor
and included their output with your issue?What you were trying to do (and why)
Use bash tab completion to show outdated casks.
What happened (include command output)
Command output
> brew cask outdated <TAB>
> brew cask outdated Warning: Calling brew cask list is deprecated! Use brew list --cask instead.
Some
cask
sub commands have been incorporated intobrew
and are deprecated (see e.g. #8390 for a helpful list), but they persist in a few places, in particular in the docs (#8629, see also Homebrew/homebrew-cask#88682). The completion scripts also use some of these deprecated commands. Beyond fixing notable offenders from cask (likelist
andoutdated
), brew sub commands (likelist
andoutdated
) also need to learn about the--cask
flag.I suppose there could be a discussion about whether to remove deprecated commands while deprecated but present/functioning.
The text was updated successfully, but these errors were encountered: