Re: MacPorts bash on Big Sur as default shell
Thanks Rainer, that was exactly the case. On Thu, Feb 11, 2021 at 7:02 AM Rainer Müller wrote: > On 10/02/2021 22.35, Mike Summers via macports-users wrote: > > I'm not able to get MacPorts bash working in Terminal as the default > shell. > > > > This is fresh install of Big Sur 11.2 on a new machine, fresh install of > > MacPorts. Only bash and bash-autocomplete are installed > > > > Setting the shell in either the Terminal preferences or for my user to > > /opt/local/bin/bash always leaves me in /bin/bash > > Make sure you use the correct command to lauch in the Terminal preferences. > See here for the details: > > https://trac.macports.org/wiki/howto/bash-completion#Terminal.app > > > The "best" workaround so far is to start in zsh which has the PATH set > correctly > > and exec bash from there. > > The MacPorts installer only added PATH to the login shell of your user > account. > For zsh, you can find the addition the .zprofile file in your home > directory. > > If you want to use a different shell, you need to make sure to configure > PATH > for that shell. For bash that means you need to configure it in your > .bash_profile accordingly. > > > https://guide.macports.org/chunked/installing.shell.html#installing.shell.postflight > > > My old machine where has been through many upgrades including Big Sur > "just works", > > > > I've run out of ideas, I'd appreciate pointers. > > Those older machines may already have the PATH settings in .bash_profile, > because you most probably installed MacPorts while bash was the login > shell. > > Rainer >
Re: MacPorts bash on Big Sur as default shell
Thanks Peter, your note put me on the right track.
What I should have done was set my default shell (with chsh or Users &
Groups) to /bin/bash before installing MacPorts bash. Then the PATH tweaks
from the MacPorts bash installer fix-up the PATH and the MacPorts bash is
always invoked.
--Mike
On Wed, Feb 10, 2021 at 9:10 PM Peter West wrote:
> I set my default shell to /bin/bash.
>
> I kept the contents of my .profile as they were, making sure to export all
> of the variables I wanted, and bracketed them with tests like so:
>
> eval profile_read=\$${USER}_profile_read
> if [ -n "$profile_read" ]
> then {
> echo `date` "~/.profile already read" >>/tmp/$USER.init_scripts
> return
> }
> fi
>
> …and…
>
> eval export ${USER}_profile_read=true
> echo `date` "~/.profile sourced" >>/tmp/$USER.init_scripts
>
> if [ -x "/opt/local/bin/bash" ]; then
> [ "$BASH" != "/opt/local/bin/bash" ] && exec /opt/local/bin/bash
> fi
>
>
> Peter
>
>
> —
> Peter West
> p...@ehealth.id.au
> “Martha, Martha, you are anxious and troubled about many things, but one
> thing is necessary.”
>
>
> > On 11 Feb 2021, at 7:35 am, Mike Summers via macports-users <
> macports-users@lists.macports.org> wrote:
> >
> > I'm not able to get MacPorts bash working in Terminal as the default
> shell.
> >
> > This is fresh install of Big Sur 11.2 on a new machine, fresh install of
> MacPorts. Only bash and bash-autocomplete are installed
> >
> > Setting the shell in either the Terminal preferences or for my user to
> /opt/local/bin/bash always leaves me in /bin/bash
> >
> > The "best" workaround so far is to start in zsh which has the PATH set
> correctly and exec bash from there.
> >
> > My old machine where has been through many upgrades including Big Sur
> "just works",
> >
> > I've run out of ideas, I'd appreciate pointers.
>
>
MacPorts bash on Big Sur as default shell
I'm not able to get MacPorts bash working in Terminal as the default shell. This is fresh install of Big Sur 11.2 on a new machine, fresh install of MacPorts. Only bash and bash-autocomplete are installed Setting the shell in either the Terminal preferences or for my user to /opt/local/bin/bash always leaves me in /bin/bash The "best" workaround so far is to start in zsh which has the PATH set correctly and exec bash from there. My old machine where has been through many upgrades including Big Sur "just works", I've run out of ideas, I'd appreciate pointers.
