Yes, Anaconda overwrote the PATh settings by creating a .bash_profile file (and editing several others). The way it does this happens deep in some python scripts (e.g. changing shell prompts happen as well). The thing is invasive.
I have removed it from my system. Gerben Wierda (LinkedIn <https://www.linkedin.com/in/gerbenwierda>) R&A Enterprise Architecture <https://ea.rna.nl/> (main site) Book: Chess and the Art of Enterprise Architecture <https://ea.rna.nl/the-book/> Book: Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/> > On 31 Aug 2021, at 11:54, Ryan Schmidt <[email protected]> wrote: > > On Aug 30, 2021, at 09:32, Gerben Wierda wrote: >> >> I had to install Anaconda (Python environment) to collaborate with someone. >> I installed, but it adapted my shell environment in such a way that I’ve >> lost MacPorts (and LMTX ConTeXt). Does anybody have experience with the >> combination of Anaconda and MacPorts and what the correct way is to use them >> side by side? > > I don't know anything about Anaconda... > > When you say you've "lost MacPorts" does that mean that when you type "port" > something it says the command is not found? If so, that means that your PATH > environment variable is not set up correctly. When you installed MacPorts, it > edited your shell startup script (which varies depending on which SHELL you > are using) to add the MacPorts paths /opt/local/bin and /opt/local/sbin to > PATH, while preserving any other additions you made. Maybe the Anaconda > installer also modified the PATH in that same shell startup file but did not > preserve your other PATH modifications. Or if you are using the Bash shell, > which supports I think three possible startup files, maybe Anaconda edited a > different one, one which takes precedence and causes Bash to ignore the other > startup file that contained your MacPorts PATH settings. >
