Remember to Reply All so the conversation stays on the list. On Nov 28, 2024, at 23:36, Steve Schow wrote:
> Thanks both of you for responding. > > So any idea what kind of work around for this? Or theory about what is > causing it? I hear you about PATH not being the reason. > > Like I said, when I run bash directly..the problem doesn’t happen. It’s only > when /opt/local/bin/bash is being used as the initial shell to load in > Terminal.app. 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.
