3 ms·
Before they changed the default the first command I had to type on a new install was $ chsh -s /bin/zsh You can’t please everybody.
by msbarnett 4y ago
Before they changed the default the first command I had to type on a new install was
$ chsh -s /bin/zsh
You can’t please everybody.
- e12e 4y agoI recommend first installing a recent bash from macports, update /etc/shells first; then change to /opt/local/bin/bash. Unless you enjoy using an ancient bash.
- Phurist 4y agoWtf, macports ? Please do your self a favor and install Nix package manager.
- e12e 4y agoI did look at nix, but was less than enthusiastic about how complex[1] the software is. If I could, I would probably prefer gnu guix - but AFAIK it is unlikely to ever support running on macos - and is similarly complex (build daemon needed to run in background). I'm also sad that pkgsrc seems to be abandoned wrt binary builds for macos - I could at least not find correct gpg keys for verifying the archives listed at: https://pkgsrc.joyent.com/install-on-macos/ https://pkgsrc.joyent.com/install-on-macos/ Perhaps it's workable as a build-from-source package manager. For now, it seems that macports have most of what I need - with less complexity than nix, and a better handling of upgrades than brew. Does appear that brew moves faster, eg: https://trac.macports.org/ticket/65922 https://trac.macports.org/ticket/65922 (i briefly tried a local build, but ran into dependency problems with libvterm that I didn't manage to resolve - there's a 0.3 [2] tarball, but the build system for neovim wasn't happy and kept finding 0.1.4 after it was uninstalled in favour of 0.3). [1] https://nixos.org/manual/nix/stable/installation/installing-binary.html#macos-installation https://nixos.org/manual/nix/stable/installation/installing-... [2] https://www.leonerd.org.uk/code/libvterm/ https://www.leonerd.org.uk/code/libvterm/