Since the existing wayland module basically describes everything about
my 'desktop environment' setup already anyway, might as well rename it
accordingly. Additionally, mako is important for notifications in this
environment so it moves here as well.
mod-Shift-M to switch to an always-unused tag for all connected outputs
to simply hide all application that can currently be seen. Would
probably be more useful with an option to reverse but that probably
requires a more extensive script to implement (perhaps using `lswt`?) so
this will be good enough for now.
I am not even entirely sure how much I will be using it.
Podman rebels if it finds an explicitly set DOCKER_CONFIG file pointing
to a non-existent (due to using podman) configuration file. Since we are
not using docker anyway, this removes the env var.
I am mostly using the TUI Mastodon client tut for any social
interaction, so here I keep its configuration. Nothing big changed yet,
I mostly like the default options, with the exception of some layout
changes.
Added hacky script to quickly cut apart dual-screen wallpapers.
I run two 1920x1080 screens side-by-side, so I just cut double wide
wallpapers in two and display one on each screen.
Script is very inflexible on probably not too useful for the future but
it works for its purposes now.
Changes the wallpaper setting code on startup to set a wallpaper for
each screen that it finds currently connected. Still a bit hacky and
should be improved for reactive wallpaper setting as new screens are
connected/disconnected but should work for the moment.
This commit fixes input locking when suspend was invoked autoatically
after a certain amount of time.
Previously, it would invoke the lockscreen first, then dim the screen
and finally suspend the machine. While suspending it would invoke the
lockscreen *again* however, which seems to lead to generally locking
input (perhaps 2 instances of waylock disable each others' input
ability?).
This change checks for a running lockscreen first before invoking
another one, which should hopefully fix the issue.
Previously, swayidle would wait for each command to be finished before
executing the next which, with lockscreen running in the foreground,
would not happen until it was unlocked again. The results were a working
lockscreen after the timeout, but nothing else happening and suspend
mode only being engaged *as soon as* the lockscreen was disabled (i.e.
when you want to use the PC again).
This removes swayidle's waiting for commands to finish and instead
simply go on to the next timeout when the time is right and should thus
fix the issue.
This commit removes the vi-mode plugin for zsh again. I have found that
the normal included vi mode of zsh is more than enough for most of my
needs.
The only two issues I have with it are that it sometimes does not
correctly go back into insert mode and it does not support word surround
commands (ysaw" for example).
While vi-mode adds the ability for such surround commands it comes at
the cost of taking longer to go into vi mode. And with my constant
switching back and for between the modes this is a much more egregious
issue than the others unfortunately.
Sometimes the leader key gets in the way. Since my leader key
combination is C-a by default, this interferes with the (rare) times
that I want to increment something in vim (also C-a).
So, this commit allows toggling the leader key in wezterm off, so it
passes through to the actual applications. You can toggle it with
`C-Alt-a`.
Commit made possible with the help of the comments in this issue:
https://github.com/wez/wezterm/issues/656
When setting the environment variable EDITOR in the shell, ensure that
the editor being set is actually available: It first tries nvim, then
falls back to micro, then nano (one of which really every distribution
should have).
Added automatic:
a) screen locking after 5 minutes
b) screen dimming after 10 minutes
c) suspending after 20 minutes
to riverwm. Makes use of swayidle to detect idle times and wlopm to
detect and toggle displays.
Lets vidl download to a temporary directory first (by default
~/downloads can be changed through "$TEMP_FOLDER") before moving
downloaded files to target directory as last step.
Massively increases download speed if final directory is on a slow HDD
or a network drive (since otherwise ffmpeg is computing on these slow
devices themselves).
