Fixed tests using new file structure for personal environment variables.
Added test cases for library environment variable and bibtex (default)
reference file variable.
Pdfs will be compiled, replacing special characters with underscores;
this fix also looks for underscored files when trying to open the
compiled version of a file.
The Library environment variable (for my default bibtex library
directory) overwrote yay's library directory; it has been renamed to
LIBRARYROOT to both mirror WIKIROOT as my note directory and keep the
LIBRARY variable empty so yay will continue working.
Binds mirror qutebrowser theming: sd/sD/sl/sL
sdD changes to dark variants,
slL to light variants. Uses gruvbox for small letters, themes mimicking
pencil/one for large letters.
I never use half the aliases that fasd provides by default. To make room
for personal quick bindings, simply disable them. They are commented
should I want to make use of them in the future.
exa is more versatile and way faster than k. I rarely used the git
integration of k (which is, admittedly, better), as well as the colored
variables. So exa should work well enough for my purposes, especially
since I make more use of vifm when cd-ing through a lot of directories.
In vim:
Use <leader>c to insert a bibtex reference in your text. By default it
is a pandoc reference (@bibref), but it can be changed to latex style
(\cite(bibref)). <leader>CM inserts a pretty-printed reference to the
selected work, using markdown styling. If you want to insert a citation
while writing, use @@ from insertmode to insert the bibref instead.
The settings add two commands: :CiteRef and :CitePretty which call the
respective functions. You can pass any amount of .bibtex libraries to
the commands and they will be available to fuzzy search through.
:CiteEdit also added to fuzzy find a source and open it in vim for editing.
The function is not working yet, I have to find a way to go from the
fuzzy finder to papis, select the correct file and edit it in vim.
In Shell:
Can cd directories (d, D), open files (f, F), open most recently used
(ru), and edit bibtex references (ref). lowercase is a weighted view
over previously used directories/files, Uppercase is a search of the
whole file structure.
Still outstanding:
Needs the same comfort function additions as vim search, especially
reference search. (i.e., open corresponding document, yank path, open
editor,...)
Will recursively look for `*.bats` files and run them with bats-core test suite. Simple sample unit tests for existing scripts are included in `.config/shell/rc.d/test`.
vifm enters last open dirs by default. vmm alias opens vifm with the pwd
as the opened dir instead. Passing along arbitrary paths to vm also
opens vifm there.
rifle is going away soon with ranger being replaced by vifm in these
dotfiles. To be prepared, and make them more universal, the fuzzy file
finder uses xdg-open to open any files.
Uses the full name of fuzzy finders instead of just their abbreviations
when warning about any of them missing, to make it clearer which
programs the warning is talking about.
In preparation for extending the scripting, renamed the script from just
being a re-aliasing of fzf. Now, all fuzzy finding logic can reside in
this file.
Fixed the quick-style .. to go up a directory. Use `cd ..` to enable the
fzf enabled selection if you quickly need to go up multiple directories
instead.
Can be set through environment variable WIKIROOT. By default points to
~/Nextcloud/Notes/ but is kept configurable for each computer. Will be
picked up by vim wiki plugin to enable wiki functionality for the
respective directory.
Should start x after all the XDG folders have been set so that aliases
etc should still work. If binds/aliases do not work (things like tm, tl,
cl and so on) then this is presumably caused by a race condition and x
should only be started *after* all directories have benn set.
Moved all personal scripts to ~/.local/bin to be systemd file hierarchy
compliant, as well as XDG compliant. Since they are not configuration
options they don't have anything to do in .config directories.
Also, it's just easier to find than the previous .config/scripts/bin.
Marty Oehme