Simply take all the mappings and move them to one big new file for now. At some point we can start thinking about splitting them up further, and if that could make sense. The groundwork is laid by vimrc looking for a maps.vim file in every subdirectory of its runtime path.
Changed to move it off Nextcloud. The synchronization should happen, if
anything, through git as a backend as intended. Since the files'
modification dates do not reflect the correct change dates, synching
over Nextcloud only ever generates conflicts.
Using the internal synch engine is preferred instead.
Whenever i3 is using gapless mode, all windows will be opaque. When gaps
are shown inactive windows will have some transparency and blur behind
them.
Script can be invoked manually with `picom_toggle_inactive_opacity` to
toggle, `picom_toggle_inactive_opacity on` or
`picom_toggle_inactive_opacity off` to set it respectively.
exa is more versatile and way faster than k. I rarely used the git
integration of k (which is, admittedly, better), as well as the colored
variables. So exa should work well enough for my purposes, especially
since I make more use of vifm when cd-ing through a lot of directories.
Use <leader><F8> to set a new colorscheme in vim. The airline
automatically sets itself to the corresponding colorscheme, as does the
tmux statusbar at the bottom.
Use <F8> to toggle between dark and light mode for the colorscheme (not
all colorschemes support this unfortunately, I might restrict the
installed colorschemes to those that do). Again, Airline and tmuxline
will automatically adjust themselves.
Tmux prefix highlight plugin has been removed, since its functionality
can be replicated easily with the ?client_prefix function in tmux -
which also works regardless of any styles applied to the statusbar
through tmuxline. Currently, whenever the prefix is active the
clock-area will turn bright blue.
Pencil is from reedes, cribbed from iWriter. It is a good, subdued
colorscheme for writing prose. All colorschemes in this vimrc now come
with italicized letters (for comments, and words that should be italic).
All themes also respect the background= dark/light distinction and
enable the respective mode.
PDFs can be compiled using rmarkdown by invoking <leader>c, or C to open
the file (which pauses vim however). The best workflow is to open the
pdf manually in something like zathura, which will auto-update when the
document is newly compiled.
HACK TODO: Added a hard-coded line to the rofi powermenu mode in
.config. Should either point to an XDG compliant rofi-modes folder
(.config/rofi-modi or smthg), or, ideally a specific directory in rofi
configuration or scripts and rofi specific dirs. That depends on the
rofi modi being seen primarily as scripts or as configuration of the
operating procedure of rofi.
Accessible through Super+Space for the quickrun menu (essentially
emulates dmenu, just with a nice colorscheme); Super+r for a more
extensive options menu: window switching, clipboard history, ssh
(accessible with Shift-right). First step toward streamlined rofi
config.
Use rofi-powermenu to show options for suspend,reboot, shutdown,
lockscreen, log out. Can be invoked with <M-backspace>. Other power
option shortcuts have been removed from quick access through sxhkd or
i3. Lockscreen can still be quickly set with <M-x>.
Lockscreen now resides in its own script to provide one source of truth,
and in case it is further customized in the future.
Themes are structured in two parts: layout and colorschemes. Both can be
set independently from each other. Layouts can make use of anchored
color values (@background, @background-focus,.. look at colorscheme
files for all available values). Colorscheme files then translate the
values into actual colorcodes.
That way, the colorscheme for all layouts can be changed with one
setting, or independently of each other. Layouts try to specify some
often used structures for rofi menus - right now there is a horizontal
list and a fullscreen options selection (which can make use of icon
fonts).
Any global theme changes should be done in settings.rasi. Any global
function changes can still be done in config.rasi. A rofi-powermenu has
been added as an example of using the theming structure. The powermenu
script loads rofi with the powermenu.rasi theme enabled. The powermenu
theme loads the fullscreen options layout, which in turn loads the
vertical list layout, which loads settings, which sets the correct
colors. Idea and original structure from:
https://gitlab.com/vahnrr/rofi-menus
