arch-linux-installation-guide VS zsh

I'm so addicted to it that I wrote an installation guide just to show off to my 'friends'. Even after months of not reinstalling, I can guarantee that I can install Arch from memory in less than 5 minutes. Arch is love, Arch is life

That's exciting! If you need any help installing, I did make an easier to understand guide, good for learning. Althought I recommend ArchInstall these days. I'm glad it can be the first experiment! I have a lot of work to do to get this thing stable. Depending on your DE/WM and other conditions, the script may throw errors so just be weary of that and don't think your system is messed up. It's just that I had no PC for 5 months and I've been back at coding for only a few days now. I rewrote the entire script and dropped probably 100 lines. Seems like I am understanding the logic behind it a lot more now and I should have a functional release this week https://github.com/wick3dr0se/Arch-Linux-Installation-Guide

You should definitely try Arch Linux! The documentation on the ArchWiki is amazing and the community is helpful. I wrote a guide on installing Arch Linux on 86_64 architecture devices and I also have a public repository on GitHub with a stripped version of my desktop with a script to automate the desktop enviornment setup. My setup uses i3wm, feh for wallpaper, thunar, xfce4 terminal, vim as IDE, very basic stuff. I made the guide, script just to make installation easier for myself, since reading the ArchWiki can be cumbersome to say the least

Check out my Arch install guide I recently made for self refrence and to assist a friend. I have instructions on there for GRUB/systemd-boot as boot loaders and NetworkManager/systemd-networkd for networking tools. I use systemd everything because it works very well and I've never had a single issue. Using GRUB in the past I had trouble removing it from multiboot setups and I'd have so much bloat from different themes and versions of GRUB. I prefer to install my boot loader directly in to my EFI system partition, mounted at /boot and then I can manage all my boot files and entries there. You should definitely check it out! systemd-boot auto detects Windows in the EFI partition. I would suggest using NetworkManager for a simple use case, it's configureless and setup just by enabling the service daemon

> Now, listen. I wish I could continue here and end with “… and this is why ZSH does it that way!”

https://github.com/zsh-users/zsh/blob/47c7bc9b1493c7374f076b... has a comment about this behaviour, but no justification. I think it's just an optimization to save a little bit of time by not forking, and to avoid having the zsh process hanging around taking resources for no reason.

As a developer, the command line is one of the tools you will be using most frequently. It can be intimidating to venture into the world of CLI tooling but I can assure you it is one of the most rewarding experiences too. In this post I want to walk ya'll through my personal CLI setup. It is based on 3 technologies which I'll coin as the "Holy Trinity" of the command line: TMUX, ZSH, & Neovim.

Just like macOS, bash is included by default in most Linux distributions. Zsh on the other hand, needs to be installed manually. The installation process varies for different distributions but you can always check how to go about it for your distro on zsh website.

POSIX Shell [sh] such as bash[bash] or zsh [zsh] are used to run the commands.

this looks like the zshell implementation.

You can mass rename, using zsh zmv module. Tutorial

I use kitty, with a Nord theme, transparency, and Zsh with Oh My Zsh, using the clean theme.