Closed hyperknot closed 1 month ago
I can't reproduce, and bash completion is just moved from .app into the Homebrew managed folder, I didn't think it is problem of Homebrew.
I mean for bash completion, isn't this line present?
complete -F _alacritty -o nosort -o bashdefault -o default alacritty
That by definition triggers an error in bash 3.2
The cask file is setup to install the bash completion that is present in Alacritty's .app
bundle.
binary "Alacritty.app/Contents/Resources/completions/alacritty.bash",
target: "#{HOMEBREW_PREFIX}/etc/bash_completion.d/alacritty"
The line you mentioned does exist inside of Alacritty's completion file.
complete -F _alacritty -o nosort -o bashdefault -o default alacritty
I see, than it's weird that the developer closed my issue with: https://github.com/alacritty/alacritty/issues/8180#issuecomment-2358581656
alacritty doesn't create any files, including the completions. So whatever you got installed is done by your package manager of choice.
Anyway, I'm not using Alacritty anymore because of these issues, I just wanted to report it here, probably the next person will also run into it.
@hyperknot I was able to reproduce the issue based on the steps you provided in https://github.com/orgs/Homebrew/discussions/5614.
Am I correct in assuming that you did not log out or reboot after changing your default login shell with chsh -s /opt/homebrew/bin/bash
? If so, doing either of these should resolve your issue with Alacritty.
@khipp Yes, I didn't reboot or log out, just restarted the terminal.
Interesting that it's not needed for the other terminals, but it's good to know that a re-login would fix it.
Closing as this is not a bug with Homebrew.
Verification
--force
.brew update-reset && brew update
and retried my command.brew doctor
, fixed as many issues as possible and retried my command.Description of issue
Installing Alacritty via brew introduces two bugs, both of which are not present in the official DMG image.
This is really some crazy behaviour when the terminal is faked in a super weird way. Only brew installed Alacritty is doing this:
Terminal.app
WezTerm:
iTerm:
The other issue is adding a bash completion which is not compatible with macOS Bash version 3.2, reported here: https://github.com/orgs/Homebrew/discussions/5613#discussioncomment-10680619
Command that failed
opening Alacritty
Output of command with
--verbose --debug
Output of
brew doctor
andbrew config