Got it thanks. I noticed in that thread some of the work arounds basically amounted to doing little tricks to /dev/null which would cause some internal things to initialize and behave normally after that. But then since then I copied over my .bashrc to this new computer and now the problem has gone away, so something about having an actual .bashrc with a few lines of stuff in it…causes something in bash to initialize whatever it needs to initialize so that this problem doesn’t seem to occur. When I was getting the error I was in the process of setting up a new system and .bashrc only had one line setting the PATH and nothing else.
Anyway, hopefully that will end up in macports bash eventually then. > On Nov 28, 2024, at 10:44 PM, Ryan Carsten Schmidt <[email protected]> > wrote: >> > The bug report I referred you to explains why it happens and the last comment > currently in that report points to a bash commit that fixes it. We would > either need to update the bash port to a version that includes the fix or > backport the fix.
