logansdotfiles/.config/.gitignore

40 lines
372 B
Text
Raw Normal View History

2020-01-19 17:02:54 -05:00
*
!i3/
!i3/**
!polybar/
!polybar/**
!qt5ct/
!qt5ct/**
!gtk-3.0/
!gtk-3.0/**
2020-03-23 04:15:06 -04:00
!htop/
!htop/**
!Kvantum/
!Kvantum/**
!dunst/
!dunst/**
Added Alacritty config and TERMINAL variable. Now I know Thomas is gonna get really pissy that I'm not using st, but frankly I don't give a shit what he thinks. What Thomas doesn't realise is that his way is not the best way. There are no best ways, just better ways. Sure, st is a good terminal, but I'm literally using Alacritty to type this message, and I like it. It is easy to configure and has GPU acceleration which makes it fast enough to literally watch a 360p video in text mode (possibly more, didn't test much since it already wiped st off the face of the planet). "aLAcRitTY is bLOaT" shut. the. fuck. up. If you cared about bloat that much you'd be using Artix, or better yet, NixOS. Instead, you're using a distro that literally stores 2 copies of every package you download and the 20 billion dependencies that come with it. You regularly bitch about how many dependencies KDE has but you haven't stopped to look at your own dependency clusterfuck. KDE is a perfectly fine desktop with plenty of features built in fully configured for your enjoyment (if you couldn't tell from my dotfiles its not my favorite, but I'll definitely admit to using KDE when I'm feeling lazy on a new install). You're probably going to say that its bloat because of that, but you clearly don't give a shit because you're still on vanilla Arch. Part of the Linux experience is being able to pick and choose your own experience. Maybe some don't want to use a tiling window manager. Sure, its more efficient once you get to know it, but not everyone is capable of learning the drastically different workflow that comes with TWMs/DWMs. Maybe they don't have the days, possibly weeks to setup everything to a usable state. Maybe they just want a computer that works. Now, I do get pretty pissed if you complain about problems that come with your choice of Linux lifestyle and A. Don't do anything to address them or B. Blame something else. Ex. Clay regularly complains about "Wine crashes all the time and has poor compatability". This was probably true back in Wine 2.0 when Clay was probably not even alive, but times have changed. Furthermore, I come to find out that the problems he is having either exist on Windows (ex. Into the Breach maximize button being useless) or are because of his WM (he uses Linux Mint Cinnamon btw). What I'm trying to say is, Thomas, be more open. Just because someone uses KDE doesn't mean that they're not good enough to setup i3. And to anyone else reading this, find what works best for you. I'm not saying to completely ignore what other people prefer, but don't just do something because someone on the internet told you to. Experiment with new things and refine what already works for you. Sorry about the rant. But hey, now that you're at the bottom, how about giving alacritty a try? If you're on Arch just go over to your local neighborhood terminal and smack your keyboard in a fashion that inputs `sudo pacman -S alacritty` into it (or use whatever pacman wrapper you want, I don't care). Feel free to steal my alacritty dotfiles too (although they're kinda basic) (if you are Thomas though you won't like the fonts since you care too much about what fonts people use). More information can be found on their Github page here: https://github.com/alacritty/alacritty Signed-off-by: Logan Gartner <logan2611@gmail.com>
2020-07-01 04:22:51 -04:00
!alacritty/
!alacritty/**
2020-09-10 20:20:00 -04:00
!picom/
!picom/**
2020-12-08 19:33:42 -05:00
!rofi/
!rofi/**
2021-03-25 02:33:49 -04:00
!sway/
!sway/**
!waybar/
!waybar/**
2021-04-12 23:50:49 -04:00
!mpv/
!mpv/**
!flameshot/
!flameshot/**
2021-11-06 16:54:14 -04:00
!neofetch/
!neofetch/**
2020-01-19 17:02:54 -05:00
!.gitignore
polybar/default
polybar/scripts
polybar/launch.sh
polybar/config