Notations will be concealed automatically on entering a textual buffer
and `$...$` style notations are contained.
Concealing can be turned off with <localleader>sV, which will toggle
concealing on or off for all notations in the file.
Additionally, the notation under curser can be viewed in a popup with
<localleader>sv.
In addition to my standard file manager, vifm, being integrated into
neovim, I have now also added a side-pane file tree (akin to nerdtree)
that is easily reachable to get a quick overview of a file layout.
For now, I do not intend to do much more with the plugin, only keep it
for those rare cases I want to have a view on my file layout at the same
time as working in a buffer. For all other things (file operations
especially) I still have vifm.
My (un-branded) usb mouse prevented the system from going into
suspend/hibernation by sending intermittent wakeup signals.
This system configuration option simply disables the device from sending
those wakeup signals. Used with superuser stow installation method.
Set up wezterm to continue to use Iosevka for everything *except*
italics (in all weights) which will instead be displayed by the Victor
font.
This ultimately results in cursive fonts for italics and Iosevka for
everything else, very pretty.
Added fidget plugin which shows the current loading status of LSPs. Only
works for a few LSP (so far), including lua and python. Should
automatically pick up new implementations on update. Will display a
small loading notification in the lower right corner, useful to display
status for those situations where LSP loading takes a long time (e.g.
rust compilation requirements or a large python environment).
FIXME Does not work for each python environment startup yet, and I am
not sure why - sometimes just does not display its loading startup.
When completing in command line I want the completion canditates to be
displayed, but *not* selected on confirmation. By doing so, it makes it
almost impossible to quickly quit with ':q' or write with ':w' for
example, as those always try to expand themselves automatically into
completion items.
This commit changes the default behavior for command mode to show
completions but not auto accept any on confirmation, instead simply
invoking whatever is currently on the command line (as if we had no
completion plugin running).
Whereas previously we had lsp-related mappings both on <localleader>l...
and g... mappings, they are now all unified under the <localleader>l
prefix group. Some mnemonics unfortunately had to give way to a weaker
version of themselves (definition becomes de[f]inition, implementation
becomes i[m]plementation) but overall I believe this to be much more
cohesive for my future lsp usage. With which-key enabled and everything
under the +l group we should be able to easily adapt to the new
mappings.
Additionally, some mappings will invoke the telescope version of their
lsp command if telescope is indeed installed, otherwise fall back to the
native neovim lsp implementation.
Switched the configuration of lsp-zero to its less integrated v2
version. Switched back to manually configuring most of nvim-cmp.
Addded some manual formatting to cmp which displays completion kind as
icons not as text.
Manually add luasnip integration.
If given <nop> as prefix mapping, the suggestions box shows *all*
mappings that exist in the program. By removing the <nop> we make the
key do its usual action but at the same time restrict the suggestions
being displayed to those actually following the prefix.
Fixed text not flowing to the external (nvim) editor and saved text not
being brought back into qutebrowser.
Same issue as here https://github.com/qutebrowser/qutebrowser/issues/6707
it essentially amounts to the terminal not having its own running
process id which qutebrowser uses to know when the application closes.
Thus, it thinks it closes immediately and deletes the temporary file. No
changes are brought back and the file is empty for the editor.
With the fix, this does not happen anymore.
If we call the listing and applying function directly we either select a
random colorscheme on *no* selection or we have to make use of either
xargs GNU functionality or something like moreutils ifne to only select
color schemes on selection.
Can additionally set a random theme (if selection is 'random') or a
random light theme (if selection is 'light').
Switching from my custom, brittle, styling implementation `styler` to
the wonder `flavours` program which does exactly the same only with more
clarity, faster and - I would presume - more stable.
