cross-posted from: https://lemmy.world/post/11419429

I wouldn’t really call myself a distro hopper, but in the last few months I’ve had to do some fresh installs on a couple of machines and VMs for work

If these aren’t included by default, I’ll make sure to get em:

GUI:

  • Firefox & Chromium
  • Gimp & Krita
  • VSCode/VSCodium
  • Okular
  • Libre office

CLI*:

  • git
  • wget&curl
  • neovim
  • zsh/ohmyzsh + plugins
  • glow
  • neofetch
  • figlet/toilet
  • zellij
  • python
  • nodejs/npm/nvm + nodemon globally
  • ranger/rifle

Also, how do you go about migrating your old config and rc files? Start fresh or just copy em over and make adjustments where necessary?

    • @[email protected]
      English
      1•5 months ago

      Yeah, very similar. And I used to use fish, but I got fed up with it not supporting bash scripts, so now I just have prezto with plugins that make it act exactly like fish 😁

      • @[email protected]OPMEnglish
        1•5 months ago

        I used to use zsh with oh-my-zsh and Powerlevel10k before I switched to fish. I actually considered going back to zsh (don’t remember why) but now I’m pretty happy with fish. What to you mean with fish not supporting bash scripts? A bash script should always have #!/bin/bash at the beginning of the file, that way it will always be executed in bash, even if you run it from fish.

        • @[email protected]
          English
          1•5 months ago

          I can’t remember the details, it was 6 or 7 years ago that I switched, but it was something at work that wasn’t working because fish used a different scripting language

          • @[email protected]OPMEnglish
            1•5 months ago

            That’s strange. If you ever want to try fish again, you can do this to avoid problems with bash scripts:

            • NEVER set your system shell (the /bin/sh symlink) to fish, it will cause so many problems. Make sure to use bash or dash.
            • Only set your user shell to fish, use chsh to do this.
            • Use #!/usr/bin/env sh at the beginning of scripts
            • If you encounter some problems, just run your script like this: bash script.sh