Added function to fuzzily search through any documents using rga.
Function code adapted from https://github.com/phiresky/ripgrep-all
Can be interactively searched, should be reasonably fast once indexing
is finished.
Added script to quickly translate a page or selected text through google
translate. Can be invoked through the aliases `:translate-page` or `:translate-selection` respectively, or the shortcuts <leader>bg, <leader>bG.
Added some gitignore files in the directory to stop keeping track of
non-personal configuration files.
The server still does not correctly ignore messages which should be
contained in the ignored keywords list. (Image upload percentages,
repository update percentages, for which it spits out hundreds of
desktop notifications. Well, 100, to be exact.)
Perhaps this simplification of the keywords makes it work better.
Added check to fetch remote updates before actually pulling in remote
changes.
This may help somewhat with the modification of files when they are
simultaneously open in vim, though I am not entirely sure.
Needs further investigation.
Session names would be cut off by the preview window.
Now, the preview window is generally *close* to the session names but
not overlapping them, which looked weird.
Moved vim-plug plugin list to load into separate file so it is a coherent
plugin list to modify or disable.
Moved key mappings (`maps.vim`) into a separate keys directory so they
can be loaded in individual files if desired.
Previously enabled the search through shell history with ^r on the
commandline. This is still the case, though now the results of the
search can be cycled through with ^p (earlier) and ^n (later).
The key combinations are only active in incremental search and will only
search through the previous results.
When in normal more, or command mode, ^p/^n will cycle through the
history of the shell, taking into account what has already been typed
and going through the history on the basis of this.
Add all `pavolume` sent notifications to a single tabstack, which means
they will be displayed on top of each other and remove the older
notification display when a new one arrives.
End result is that volume changes are now displayed as continuous
changes of a single notification (i.e. changing volume level bar)
instead of multiple notifications.
Enabled zsh option to automatically prepend directories with `cd` if
they are the only command on the line, essentially enabling you to just
write `/var/lib/docker` to go to the respective directory.
vifm switched to a new json formatted vifminfo file,
see https://sourceforge.net/p/vifm/mailman/message/37115461/
This commit simply adds it to the ignored files list, since we do not
care to have it in the repository just like the old vifminfo file.
`:ScratchPad` command has been fixed and its functionality slightly
extended:
`:ScratchPad` will replace the current buffer with an empty scratchpad,
with the filetype defined in `g:scratchpad_ft` (or the buffer-scope
equivalent).
`:ScratchPad!` will create a new split and open the empty scratchpad
there.
Additionally, a single argument can be passed to the command with the
name of the filetype that the scratchpad should contain, e.g.
`:Scratchpad! golang`
Most of the plugin process has been shifted to lua and only a single
command mapping remains as vimscript for now.
Previously the key was space (when in vi command mode), but that can too
easily be accidentally hit.
Using ctrl-e (when in vi command mode) makes mnemonic sense ('edit'),
and is hard to hit accidentally. It also mirrors the c-x c-e mapping
that bash (and zsh?) use when in emacs mode rather than vim.
Allows pressing <alt-.> when in insertion mode in zsh to add the first
(then second, third, ...) argument from the last line to the end of the
current line.
Especially useful for things like:
```
mkdir -p my/folder/deeply nested
cd <alt-.>
```
to instantly move to the folder!
signature help shortcut (<c-k>) was interfering with basic buffer
movement. Moved it to gK as a more 'global' hover option (which uses K,
whenever lsp is enabled).
Add readme markdown files to stow ignored list so they will not be
automatically linked in the home directory. They exist purely for the
repository and should not appear on the system itself.
`udiskie` is kept running in the background and automatically
mounting any inserted media, which will then also show its
tray icon so that it can be quickly unmounted as well.
Additional ideas would be to allow mounting / unmounting through
keyboard sequences instead of gui (via rofi for example).
Added new functionality to lsp: hovering, go-to definition, referencing,
implementations, etc accessible through the usual hotkeys.
Added commands to invoke LspHover and temporarily disable lsp for the
current buffer (is re-enabled on re-entering the buffer, e.g. with
:e<cr>)
Added tjdevries extended lua lsp implementation containing functionality
for the nvim api itself (especially useful for `vim.api`, `vim.fn`).
Previously, the foldlevel of 2 would still display second level markdown
headlines (`##`) but fold `###`.
However, most of my text analyses are taking place within 3rd level
headlines nowadays, and if vim-pandoc is allowed to have folds enabled,
it will always fold everything beyond the foldlevel *each* time you
enter a buffer of pandoc filetype.
So, simply up the foldlevel one.
Cursor movement works better for soft-wrapped prose files now:
When just using j/k to move vertically, the cursor will jump between the
different parts of a single wrapped line. That means you can easily move
anywhere you want on your lines, exactly as it's shown to you.
If, however, prefixing your j/k move with a number to move a relative
number of lines, it will no longer take wrapping into account. That
means you can not jump instantly to *any* part of a wrapped lines,
however on the other hand the relative line numbers on the side never
lie now: You will jump exactly as many lines as are shown on the side.
This is a tradeoff I am happily willing to make.
Additionally had to remove vim-pencil to get the movement to work, but
since it did not provide any visible pros anymore, this should not be a
big issue.
tab and shift-tab will select up and down,
ctrl-g moves to the first entry,
ctrl-t toggles the preview window on and off,
ctrl-d/ctrl-u scroll through the preview window.
By default, a preview window of the contents of whatever file is
currently selected will be displayed.
I would rather have the preview hidden by default, but it is hidden in
the default options it becomes hard to show it automatically again for
individual commands, so this seems a better compromise.
completion-nvim chaining seems to not allow multiple `triggered_only`
definitions in the same linked chain of various completion options. In
other words, when in pandoc files there is no possibility to have
completion for lsp and buffer words by default and for paths on pressing
`/`, as well as bib-citekeys on pressing `@`.
Doing so requires automatically switching sources, which in turn is of
little use when writing pandoc normally and it hangs every couple of
seconds to recompile the bibtex list as soon as it runs out of buffer
words to complete.
Ideally, the completion-nvim bug should be looked at, but also the
bibtex completion possibly completely turned into a lua parsed
completer, so it does not depend on `vim-pandoc` and its (presumably)
slower vimscript implementation.
Make use of colorful action groups and query input option.
By default, will group the different completion actions (if they have
been set up for the respective zsh completion) as different color sets.
When entering an input and nothing fits (or something else than
intended), it is now possible to simply hit alt+enter instead of just
enter to add whatever you typed into the zle instead of whatever fzf
provided you with (or nothing at all, if it didn't).
Fixed source completion, so it automatically changes to turn source
switching *off* for pandoc files (to not automatically invoke bibcite
generation), and *on* for the rest of files.
This was accidentally switched the wrong way round before.
Lsp will by default invoke most of its sources simultaneously (one after
the other if no completions are found for the first), but this is
disabled for pandoc.
In pandoc, only the buffer and lsp sources are invoked (the first
chain), since bibcite will take a while to compile the cite keys.
To invoke bibcite in pandoc, use c-j/c-k when in the completion menu,
and they will be calculated.
This may be removed if a faster compilation for bibtex citekeys is
found.
Enabled lsp within nvim and switched completion engine from deoplete to
completion-nvim.
The completion will be somewhat more barebones for some filetypes until
the language servers are set up, but should then (theoretically) carry a
lot more features than before.
Additionally, we can, over time, add additional code inspection
functionality.
One change concerns the calling of bibtex cite key completion in pandoc
files: Where before the completion would automatically begin after
typing an '@', it will now only start on manual completion invocation
(c-p/c-n) -- since the completion from my current bibtex file takes a
while to load.
Changed function to accomodate internal change in wiki.vim naming for
the link parsing function.
See wiki.vim commit d085c138fd4cd33abeb93f1c1afaff1210c7c33b.
Added filtering by dump tag *or* folder to afew so that incoming mail
should automatically be filed exclusively in inbox or the dump for
notmuch.
Additionally changed the exception for inbox display from list to dump
tags in aerc, so that -- should there be a legitimate mailing list mail,
such as gitlab's pipeline reports -- they are still visible in inbox.
Improved completion menu by allowing c-p,c-n scrolling through it.
Removed automatically resizing buffers, use c-w= if you need it.
Added scrolloff, controlling the amount of lines that are always
under/above the cursor. This fixes the cursor being at the very bottom
of the page, after doing e.g. zb or zt and will allow seeing a bit more
information around it at all times.
The module will pick up the current state of the systemd mbsync.timer
and display an according icon (sleepy bell if auto-sync is off, mail
icon if auto-sync is on).
It will use notmuch counters to show only unread mails in the inbox,
which generally constitute the 'new' mails one wants to know about.
It will not display anything if it did not find 'new' mails.
Lastly, right-clicking allows starting the auto-sync timer and left
clicking allows to stop it.
FIXME: The icon will only update on the next update interval of the
module itself (which is set at 300 seconds). That means, after clicking
the icon to start or stop the auto-sync, the actual state will not be
reflected by the icon for a couple of minutes.
Detect X autostart a bit better with a separate service. The service
relies on a shell script which searches for a socket which X creates on
startup and only finishes when it finds the socket succesfully.
This makes services which need X to start successfully a bit more
robust, and while it can still break if X takes too long, it should be
more stable now.
Finally, services can restart more quickly when ended since they don't
require the 2+ `RestartSec` option to be present anymore to successfully
start.
Update `mail-check` script to notify the user both of newly arrived
mail, and in case he has to enter his password to sync the mail.
HACK the paths and ways of finding out if passwords can be decrypted are
static and only applicable to my set up. This needs to be completely
revised and newly approached.
When called over systemd, pass will not display a pin-entry field to
decrypt the necessary passwords for email synching.
This prepares automatic background synching.
Fixed running the hooks for `mail-check`. Command (or variable?)
substition prevented the hooks from running completely beforehand, so I
moved them to a separate function with the option remaining to call a
custom script for them through environment variables.
Ideally the env vars (`MBSYNC_PRE` and `MBSYNC_POST`) should only point
to a single script each, as more involved commands will presumably fail
to execute correctly when whitespace substition is involved.
See more explanation here:
https://unix.stackexchange.com/a/444949
