This sets the cursor to breeze_cursors by default in our window manager.
Now we have a universal theme cursor for both the window manager and
GTK / KDE applications.
wal.vim includes a color scheme for lightline, but it only plays nicely
with neovim. This commit conditionally loads the wal color scheme since
using it in vim will throw multiple errors.
The solution I used previously for padding in termite did not change the
padding color when other software such as pywal changed the color scheme.
This fixes that, so now it is possible to change color schemes
fully in termite without having to spawn a new terminal. This is
very nice, and also works well with termite's transparency feature.
Instead of manually changing every instance where a program could run to
use the config in the cache directory, and instead of copying files
every time pywal is updated, it makes sense to create symbolic links for
these files instead.
This ensures that the right settings are used even without knowing the
passed parameters.
Since tmux is such a useful program, and since we don't need to worry
about images in termite, it makes sense to start all termite windows
with tmux. This lets us use any and all termite sessions in urxvt as
needed.
Before pkill would try to terminate the script since it had "dunst" in
its name. This is the solution for that, and it also makes adding new
commands in the future easier.
Termite works exceptionally well as a transparent terminal, so I'll just
let termite focus on true color, transparency, and displaying emoji
while urxvt focuses on universal theme changing and images in the
terminal.
There doesn't seem to be a terminal out there (yet) that handles both of
these things in all the software I want, so this compromise is good
enough.
With these settings, the cursor looks exceptionally well even with
HiDPI. Adapta is used over other GTK themes since Adapta has very good
padding defaults. Adapta also won't cause problems with input fields,
compared to several other GTK themes.
After comparing environment variables between KDE Plasma and bspwm, I
finally figured out that QT_SCREEN_SCALE_FACTORS was needed as well for
full HiDPI support. With this setting and QT_FONT_DPI applied, KDE / Qt
applications now look exactly as they would in Plasma.
To avoid any differences that may arise, I also exported XDG_DATA_DIRS
and some other variables set by Plasma.
This is the last commit I will make regarding Plasma with bspwm
support. This script is required to start Plasma with bspwm, although
it is much better to run KDE applications from bspwm instead.
This commit makes the post-wal script a bit more aware of its
environment. This is only to support Plasma with bspwm, which
needs the bspwm settings but not the dunst settings.
Since bspwm with KDE settings performs exceptionally well, I may drop
Plasma with bspwm support altogether and revert this commit at a later
date. The overhead of wmctrl and grep may not be worth it.
Additionally, the filename should probably be changed to a more
generic one in order to support more software as needed.
Since Plasma does not respect feh, it makes no sense to set a
background for it.
Note that these settings apply to Plasma with bspwm, *not* bspwm with
KDE settings. You should not have to use Plasma with bspwm, since bspwm
with KDE settings should do everything you want and much more.
In the future, I may remove Plasma with bspwm support altogether.
Since wal is used to manage the color scheme, it needs to be started
when running KDE Plasma. This script does just that.
Note that the desktop background is not changed (-n) since Plasma uses
its own background manager and does not respect feh.
Instead of starting urxvtd with urxvtcd, start it automatically with
systemd. This lets us run urxvtc directly in other desktop environments
without having to rely on urxvtcd.
Although I use stow to manage my dotfiles, the way you need to invoke
stow is different depending on where the dotfiles directory is located.
To circumvent this, I wrote a Makefile that automatically determines
the stow directory (the parent directory) and package directory (this
repo) before calling stow.
Previously I separated my .vimrc into multiple files in attempt to
organize it. Now that I know more about vim, however, using only one
config file leads to less moving parts. Additionally, I now use less
vim settings altogether since I frequently have to work on foreign
machines, which probably won't have my .vimrc anyway.
Rofi is "a window switcher, application launcher, and dmenu
replacement". It lets you search for and access certain
information at any given time, making it very useful.
pywal (also known as wal) lets us change color schemes with a cache
directory instead of editing config files directly. This helps us
separate the dotfiles from the color schemes.
This commit removes explicit color settings from my dotfiles, which are
now managed by pywal. Dunst has been added to show any notifications
that I may want to use in the future. The colors.Xresources file is used
to prevent urxvt from using a depth of 32.
My custom colors.vim file has been removed in favor of wal.vim, which
solves some problems I had to manually resolve myself and should make
things easier to maintain in the long term.
Note that pywal also supports base16 color schemes, as well as any other
color scheme you can think of.
Lots of changes here. SXHKD_SHELL is used to specify bash as the shell
to use for sxhkd. This is required since we use bash-specific syntax in
our sxhkdrc. Many commands that once ran through .xinitrc are now
executed by bspwmrc instead, and additional rules have been added to
support KDE applications.
Here I finally figure out how icons work in Arch Linux (and probably
other distributions as well). Other changes include a smaller font size,
more gaps, and less line size.
Manually overriding fonts caused problems in some applications. With
DejaVu and other common fonts installed, there *shouldn't* be a need to
use fontconfig anymore, although I haven't extensively tested this.
Instead of stowing dotfiles individually by software, and instead of
stowing dotfiles based on working environment, I now just stow all
dotfiles at once, so the extra hierarchy isn't needed.
I am back to using a PKGBUILD to manage my packages. This makes it easy
to manage packages on multiple machines with pacman and keep track of
which packages were installed.
I have decided to dedicate this repository solely to my dotfiles, which
for the most part should work on any GNU/Linux distribution, not just
Arch Linux. Separating the scripts from the dots should make things a
lot easier to manage.
