We actually still need compton (now picom) for screen tearing in bspwm,
so we'll add it back now. In the future it may be useful to keep
dotfiles in the repository even when I no longer use them, since the
configuration itself may still be useful.
So far my experience with LunarVim has been positive. Although there are
some gotchas and your own configuration may be better in some cases, the
defaults used are pretty nice and should enable developers to get up and
going quickly with neovim.
I like how sway handles workspaces. This change makes it so bspwm uses
numbers as the workspaces and polybar only shows workspaces that are
being used in the bar.
Although alacritty is cool, kitty is also cool and has image support,
ideal for rice screenshots.
This commit also adds $alt for the rofi command in the previous commit.
After the contest for archlinux-wallpaper, there are a lot of high
quality backgrounds that one can choose from. Instead of worrying
about choosing an appropriate background for a desktop environment,
one can simply use archlinux-wallpaper instead.
$hostname is now defined by default so we don't need to do anything
here. I assume it wasn't always like this since otherwise I wouldn't
have needed to call `hostname` in the first place.
This admittedly makes our tmux slightly boring in comparison to those
that customize it, but having a consistent layout makes it easier to
work with tmux across different environments.
"dog" was an alternative I used to cat for syntax highlighting. Now that
bat exists (which is written in rust, by the way), there is no need to
use "dog" and I highly recommend anyone interested to use bat instead.
It turns out that I don't actually *need* image output in the terminal
(besides being cool). With that aside, I can safely use alacritty
knowing that it's written in Rust and is apparently the fastest terminal
emulator in existence.
Note that I need to update the script later or simply provide a series
of instructions so everything isn't dependant on one script.
In the past it was nice to install Arch Linux with minimal if any
console intervention, but the practicality of this is questionable
since you only have to install Arch once. A more specialized script
could be useful for mass installations, although in this case I assume
one would create such a script on-the-spot.
For those of you reading this: If possible, you should invest in neo(vim)
instead of (vs)code, as I believe there is a significant difference in
productivity when it comes to not worrying about the user interface that
(vs)code provides.
