Using ps -e is not that helpful since it does not show the full command
line which is what is helpful in filtering and distinguishing between
multiple processes. For eg. we might have multiple processes running
using python and to distinguish between them we need the full command
line invocation.
The battery percentage feature relies on the experimental flag being
passed to the bluetooth daemon so that the bluez experimental API
can be used for battery percentage indication.
For some reason, BROWSER always gets set to firefox instead of
firefox-wayland which is our own desktop file for starting firefox
in wayland.
Setting the systemd environment variables or using the env in desktop
file has not helped.
sway seems to not start at all when using lightdm to login. We disabled
lightdm and now just use the login shell to start sway. sway never
recommended login managers so this was long due anyways.
See https://github.com/swaywm/sway/wiki#login-managers.
They frequently get clipped beyond the window border due to being too
long and are not that helpful.
While at it, use our own preferable default sane options for the rest.
We pick up the compiler cargo file from rust.vim as the errorformat
seems better perhaps to consider a few more things compared to the one
included in neovim.
It has a few more things than asyncdo and automatically handles makeprg
not that setting a custom command to handle makeprg with asyncdo was
a problem but still. Should also be useful for fugitive git push,
believe it will use dispatch when available.
See the actual fix upstream
32ddc125ec
This could be probably unrelated and just was fixed in neovim core
perhaps. Either ways we do not need to do this anymore.
Not sure if we ever really needed this considering that we work on open
source projects, where we need only push the branch from which we raise
the MR. Pretty much the same for current client work as well. Are tags
ever required for such scenario?.