Distro hoppers, what's always on your install list when you've finished setup and logged in for the first time?
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?
11 replies
htop, midnight commander, nettools (ping, ifconfig), nmap, ssh server
You don't use iproute2?
I personally always install
For terminal usage I install:
I just pull down my ansible playbook from github and run it.
Would you mind sharing the link to your repo?
Zsh with prezto and some sort of guake-like
What does prezto do? Is it similar to oh-my-zsh? Have you ever tried fish shell?
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 😁
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/bashat the beginning of the file, that way it will always be executed in bash, even if you run it from fish.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
That's strange. If you ever want to try fish again, you can do this to avoid problems with bash scripts:
#!/usr/bin/env shat the beginning of scriptsbash script.sh