nvim: Restructure lua config directory
Restructured lua setting files, so that plugin settings are in clearly
labelled as such files, and the base files are just there --- the base
directory.
This should also lay the ground work for modularizing plugins, so that
we can enable/disable plugin groups as we need them.
----------
nvim: Remove ale linter and formatter
Removed ale from plugins.
Linting is being taken care of by lsp and treesitter plugins and
formatting by formatter.nvim.
Added all filetypes ale took care of to formatting on save.
----------
nvim: Replace wiki.vim with zettelkasten.nvim
Removed lerlvag's `wiki.vim` from plugin list.
Though I love it and loved using it, by now it clutters up the list and
the basic functionality I need it provided by zettelkasten.nvim.
(That being linking, following links, and quickly opening a central file).
I may still come back to it at some point, but for now I am happy with
the new setup.
----------
nvim: Add toggleterm and lazygit integration
Added toggleterm plugin, integrating a very quick access to the neovim
terminal (`<leader>=` mapping).
Additionally, added a command to quickly call up a lazygit floating
windows with the same plugin. `<leader>G` will open a git management
window in which you can stage, remove, commit, push, pull and more.
----------
nvim: Replace surround, sneak; Add treesitter, dial
Replaced vim-sneak with lightspeed lua plugin, which accomplishes
similar to the same goal, with a little more flexibility (can also be
used to replicate other vim plugins like e.g. easymotion).
For now I am using it as a straight replacement, with the same fF/tT
functionality stretching over multiple lines, and quick sS 2-letter
jumps to any location ahead/back.
The highlighting is noticeably more stable and faster. For now it is set
to always highlight the next 5 occurences of a letter, wherever they
are. Lastly, it does not -- so the lightspeed author -- change the
buffer in any way which is what happened with sneak (due to vimscript
limitations) and which can and did confuse things like treesitter and
the lsp integration.
Replaced vim-surround with a lua-equivalent surround.nvim. This one I am
less sure about, the lua pluging, while working, still carries some bugs
and does not seem as thoroughly tested. It still has problems with
surrounding stuff with e.g. `*` and does not deal well with some
quotation situations. I will try to keep using it and perhaps find the
time to contribute to some of the issues instead of going back at first
however, purely since I am a much bigger fan of the plugin existing in
luascript.
Replaced vim-peekaboo with registers, another switch to a lua plugin,
which also functions slightly differently however. I much prefer the lua
plugins display of register contents which simply appear as a dropdown,
compe-like, and I can either paste with the correct symbol choice as
always, or by scrolling through it as if it is an autocomplete choice.
Added dial.nvim which slightly extends the functionality of ^a and ^x
number in-/decreases. It should barely be noticeable in normal operation
but now the combination can be used to change dates, alphabet
characters, hex codes and some more. Most prominently, I am using it for
date manipulation.
Added a couple of treesitter related plugins:
treesitter-context shows the context the cursor is currently in if the
beginning of this context goes off-screen, e.g. the function beginning
or current class being edited. Works for nested contexts.
treesitter-textsubjects allows selecting units of codes by going up the
tree branches. So, first you select an argument, then the whole argument
chain, then the function definition, then the whole function, then the
containing class, and so on. It is quite natural, however, I have so far
only made it work for visual selection, so not as a motion target.
Still, very useful - works with `v.` and can be repeated with `.`.
Lastly, ts-context-commentstring improves the correct selection of
commenting type for commenting plugins (i.e. my `gcc` mapping), by
making use of treesitter where available. Can even do multi-language
files like vue, react, or tsx modules with html, css and javascript
interweaved.
----------
nvim: Add code formatter
Added code formatter in lua, right now supporting python, cpp,
javascript, lua, rust.
More can very easily be added.
I am not sure if this plugin supports the formatting of code within
snippets in another file format (lukas-reineke/format.nvim does support
this, but seems not-maintained).
----------
nvim: Add tmux, snippet completion
Added (for real this time) tmux adjacent buffer completion.
Added vsnip completion through compe: Invoke a completion (shown in
compe with snippet preview) through <cr> or <space-cr> and then use
<tab> and <s-tab> to go back and forth through the completable positions
for the respective snippet.
Many default snippets included through the community repository of
friendly-snippets.
----------
nvim: Improve compe completion, Add outline view
Added outline view to neovim, similar to the well-known vista.vim
plugin. Can be opened (and closed again) with <leader>o mapping, simply
mnemonic for 'outline'.
Added unicode symbols (invoked with '\') and tmux adjacent buffers
to compe completion sources.
----------
nvim: Add zen writing mode in lua
Switched from goyo to TrueZen.nvim in looking for a lua replacement of
zen writing modes. The F11 shortcut remains the same, additionally using
F10 shortcut to enter a less drastic minimal mode.
----------
nvim: Switch keymaps to lua format
Using cartographer to make setting keymaps easy.
----------
nvim: Add tmux Navigator lua replacement
----------
nvim: Add autopairs, zen writing lua plugins
Switch goyo and autopairs to make use of lua plugins.
Moved most of the plugin setup code from a custom and manually updated
array being called from init.lua, to their respective plugin
installations in plugins.lua (so, wherever the plugin is installed also
contains the call of the configuration code).
This should hopefully reduce duplication a little and may prepare for
the lua plugin setups to end up in plugins directory of neovim.
----------
nvim: Add lua statusline, base16, async grep
Added galaxyline in an initial iteration which is probably overloaded
but integrates well with the also moved over to lua base16 colorschemes.
For now, it is possible to, at any point, simply call the `:lua
B16theme('themename')` command to change the colorscheme of both neovim
itself and the galaxyline with it.
The statusline, as of now, includes the activated mode (of course), the
filename being edited, the edit state (whether changed from last save,
or read-only), the current git branch if any, as well as the amount of
added, modified, and deleted lines from current git commit. On the right
hand side it contains the lsp status (if connected), the amount of
errors and warnings in current file, the filetype currently recognized
for the file, as well as the usual cursor position in the window.
Added some small other things, including an asynchronous fuzzy-backed
full-text search through telescope, which should hopefully make
full-text searching much more responsive than before; updated the
version of indentline to the correct one; and disabled some unused vim
built-in plugins.
Switched to a lua setup. Moved from `init.vim` to `init.lua`. Moved to a
lua-based plugin manager (packer.nvim). Moved some plugins to neovim
(i.e. lua) versions instead of vimL (notably fzf and indentLine).
Enabled lsp, treesitter and similar plugins by default.
Modularized plugins a little by invoking them in separate files.
This should provide a base to build on, and allow me to more fully
integrate lua into my workflow.
More detailed changes follow:
nvim: Replace completion-nvim with nvim-compe
Replaced completion-nvim since compe comes with more things working out
of the box (especially buffer completion and treesitter save me two
plugin installations), and seems to be overall a bit better supported.
It's fast, it works well, and I can add custom completion sources so
that should be good enough for me.
Changed around a couple of other things for lsp settings and treesitter,
and moved the files around a bit.
This is somewhat in preparation for a move to a lua-based configuration,
since I have long wanted to make the switch.
nvim: Add treesitter-enabled rainbow brackets
Added rainbow brackets to the editor, using the treesitter AST
detection. I am not sure yet if I will keep them, or if they confuse me
more than they help by coloring *everything* *everywhere* and being a
bit too much for my tired eyes.
nvim: Add vim-terminator to enable repl style dev
Added vim-terminator and included some basic keybindings. The plugin
allows sending code over to a terminal window, or repl for those
languages where it's enabled (python, R, bash somewhat).
The basic workflow for me right now is: From e.g. a python file
1. Open a repl with <leader>rr
2. Send over code with
2a. <leader>rt sending (selected part or whole of) file over
2b. <leader>rd sending (selected part or whole of) delimited area
over
A delimited area in option 2b looks for certain patterns and sends
everything up-to the next instance of that pattern.
Currently, the enabled patterns are `In[n]:` with n being a number,
emulating the way jupyter blocks are coded; and `^```` (three
back-ticks at the beginning of a line), to enable sending code fences
from (R)markdown files.
Since it uses the filetype to determine which repl/interpreter to send
code to, it is still a little unwieldy in markdown files (which in this
editor get handled as `pandoc` filetype.)
FIXME: There are two options going forward, either finding a way to
correctly identify the interpreter without filetype (should be done in
vim-terminator and seems inelegant) or correctly setting the filetype
for code fences in (R)Markdown *only* (seems more feasible and may
already be enabled in RMarkdown plugins for vim).
nvim: Fix simultaneous opening alacritty and nvim
When opening both (e.g. `alacritty -e nvim file`), neovim would open
with the wrong size (usually way smaller than the resulting terminal
size) and stay that way until you resized the terminal window.
This simply sends a 'resize' kill command to vim whenever the user
enters it to circumvent the bug until it's fixed.
nvim: Simplify lua plugin setup, Add indentLine
Added indent line plugin to show where and how indentations occur using
neovims virtual text. Can be toggled with `:IndentBlanklineToggle`.
Simplified lua setup a little by naming settings after intent instead of
per plugin -- everything lsp-y now resides in `lsp.lua`, everything
treesitter in `treesitter.lua`, everything indentation in its respective
file. Should, as long as plugins don't get too many, be perhaps a little
simpler to reason about.
nvim: Switch to packer as plugin manager
Switched to packer -- the plugins move to lua and so will I. Packer
seems basically like `vim-plug` in a dress (which is awesome, since
vim-plug is also awesome!) and it is extremely fast.
So, no real complaints but still a little switch to get that little bit
further away from vimscript.
nvim: Add telescope plugin and configuration
Added telescope as fzf replacement. Fzf served me well, but the
configuration is somewhat difficult (not least owing to the fact it's
written in vimscript), and telescope has a burgeoning ecosystem growing
around it.
I could basically drop-in replace all of my mappings and then some.
Refined some options and changed some defaults and I am fairly happy for
now.
nvim: Switch to zettelkasten plugin over wiki.vim
Added lspsaga to enhance some of the lsp actions I can do - mappings are
mostly the same as before, pretty much all lsp actions can be invoked by
g<mnemonic> (e.g. `gr` for rename, `gh` for symbol help, `gd` for go
definition, `K` for help hover, `gc` for code completion and some more).
`[e` and `]e` move between lsp diagnostic errors.
Switched out many syntax highlighting plugins for treesitter, which is
an experiment for now, but I would love to keep it like this if it works
out.
Simple, experimental replacement for now. Tries to keep the previous key
functionality intact:
use <leader>e to open working directory in vifm, <leader>E to open the
directory of the current file.
Some problems will remain - currently it is hard to navigate away from
an open vifm instance with C-hjkl since it is not recognized as a vim
window anymore.
Additionally, invoking vim functions does not work from the vifm window,
which means that if I start nvim pointing to a directory, i.e. with vifm
open, it not possible for me currently to directly start up fzf to open
another file, or a buffer from the history, or similar.
Removed display of time and date from tmux, since I have the polybar
time up always.
Shuffled around the rest of the display: removed left-sided display of
active (tmux) user, moved it to the right side.
`: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.
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`).
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.
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.
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.
Made yank highlight last 0.5s instead of 0.15s.
Moved mapping to display toc for markdown and pandoc files to the vim
standard mapping of gO (by default only enabled for :Man and :help).
Uses :WikiFzfToc, so will only work with wiki.vim
Fix location of thesaurus to follow XDG specification for application
data (in `.local/share/nvim/thesaurus`).
Automatically download thesaurus if it is not found.
Fixed navigating backwards ignoring any files jumped to via the
Zettelkasten function and only moving to the last wiki.vim jumped-to
file. Now correctly navigates to any file in the chain, be that zk or
wiki by invoking the correct wiki.vim page opening function.
Can move through wiki by Zettel anchor IDs. Replaces standard wiki
movement. Zettel IDs do not care about the directory they are in, as
long as the ID is the same the Zettel can be located anywhere within the
wiki root directory.
Will need refinement and speed improvements in the future.
Whenever I write markdown, I want it to be interpreted by pandoc rather
than markdown itself. I write the pandoc flavor of md, I want the pandoc
plugin to handle the files, and I want to enable citations and
compilation in every markdown file.
Added fzf as selector interface for spell correction
selecting. Can be invoked through command
`FzfSpellSuggest` for now. Can be bound to keymapping if needed more
often; or if intending to overwrite default spell correction.
Fix various little fzf annoyances: Implement good coloring of floating
window. Make it use fd by default, search through hidden files but
ignore the git directory itself.
Also, let it split the window on s and vertical split on v.
fzf already comes with its own floating window call function, so we
don't have to use our own. Instead simply call the floating window when
we are in compatible vim/nvim version and let fzf do its thing.
By default fzf now uses a floating window covering most of the editor
screen real estate. It can still be full screened with a bang.
Floating window can be made optional with fzf layout options, but for
now I will try it for all fzf searches to get a feel for the positives
and negatives.
Added thesaurus calling on leader-zt, for word under cursor or selected
word(s). Will go through variety of online api's or locally supplied
mthesaur.txt from project gutenberg.
When creating a new link within notes, using the wiki.vim openlink
shortcut (return by default), it will prepend a Zettelkasten-like unique
id based on current time in front of the link.
It will also lowercase it and substitute spaces for dashes.
wiki.vim overwrites omnifunc for any buffer it sees as its own. Pandoc
uses g:pandoc#competion#Complete as its omnifunc to generate citations.
So we use deoplete to collect the citations and display them on being
invoked by `@`. When typing more, it filters the list accordingly.
Have not gotten preview window working again, nor searching of fields
other than bibkey.
Setting everything during PlugLoad function caused some plugins to
misbehave. Plugins are now loaded by Plug and their settings can be
either set with a file in the plugin directory (this mimicks the old way
of setting plugin up during load) or in after/ directory, which sets
options *after* everything has loaded.
