-
Notifications
You must be signed in to change notification settings - Fork 1
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
Buncha "have: command not found" errors in bash #10
Comments
Almost certainly completion:
etc |
|
Certainly mixing macports and homebrew is weird, and might introduce conflicts since neither is reconciling with the other, but I don't know of any specific conflict offhand. |
Ah, good catch. I did a I've got an oddball system here, and it's probably due to that: up until recently, I was a macOS 10.14 Mojave holdout, and thinking about migrationg Octave.app to MacPorts, so running MacPorts for the last couple years, and then recently added Homebrew back in. And set up these dotfiles to conditionally load them, but seems like you can't easily fully conditionalize loading in MacPorts. Or, more likely, I'm just doing it wrong. I think I'll prolly just uninstall MacPorts here, and stick to one or the other of it or Homebrew on each machine. Thanks, @aredridel! |
For the last week or so, when I fire up
bash
from inside a zsh session inside a Mac terminal (iTerm2) using these dotfiles, I get a bunch of error messages like "bash: have: command not found".I don't know what would be calling
have
; I don't seem to be doing so inside my bashy dotfiles here.Maybe it's some bash completion thing? https://stackoverflow.com/questions/12874920/have-keyword-for-bash-completion
Symptoms
No idea what's going on here. I don't see any
have
calls in my dotfiles.This is on at least angharad, my macOS 14.2.1 iMac on Intel Mac.
TODO
The text was updated successfully, but these errors were encountered: