In preparation for at some point leaving flavours in favour of tinty
(since flavours is not maintained anymore), started preparing a rough
translation of the config file for the new program. One of the things I
changed (to make more semantic sense) is the zathura colorscheme file
name.
Simple wrapper for xdg-open functionality. Simply refers
to xdg-open except if there exists mimeo on the system
which it will refer to instead.
So, a simple preference modificator for mimeo over
xdg-open since that is my preference too.
Also gave it a short name so I can do open whenever I
want and don't have to tax my left hand with tying xdg.
Do not open multiple pdf files in the same window, but open
a new window for each file opened (there is no way to
display multiple open pdf files side-by-side otherwise).
Added hjkl mappings to scroll within pages. Added movement
between highlights with `]h/[h`, although I am not sure it
works in both directions with these mappings.
Since sioyek does not support including into its configuration
file, we switch it to dotter templating and use the in-place
flavours insertion on theme selection for theming.
Any theming will not back filter into the repository.
HACK Since there is some weirdness with the whoosh backend for papis not
being able to either index or search for integer values in custom
fields, this commit sets the priorities across the library (as well as
the tui picker) to make use of textual reprentations.
1 -> high
3 -> medium
5 -> low
This means we can't do simple arithmetic evaluations on priority anymore
but at least we can search it correctly in papis. Should probably put in
a ticket to see if it can be fixed.
The `papis tags` command is extended with the functionality to not
just display all tags used in current query, sorted alphabetically,
but also to display how often they appear.
Use `papis tags -c` to show a space-separated count of how often
each tag is used next to the tag name, in descending order.
Replaced or extended all default references to zathura with
sioyek so it will automatically take on any tasks meant
for pdf reading. With the current configuration, hardly a
change should be noticed.
We render the priority of an entry in both table and multiline mode,
with priority >=1 being highest, >=3 being medium and everything
>5 being low priority.
We also have some maps for quickly setting the priority of an entry
from the tui:
`,ph` | `,pm` | `,pl` (for high, medium, low - so 1,3,5).
Lastly, I quickly added some to-dos that require the input of the
maintainer or some work in a fork, so I don't forget.
I also should not forget that I implemented some of them locally already
and am using them.
Mimicking my move from master branches to main,
now my overall general library also resides in 'main'
instead of 'master'.
No real visible change, but unifies the wording for
everything.
Unified key bindings roughly to
localleader=, anything with `,` in front will affect the current
documents somehow (e.g. mark them read, add a tag, ..).
jumpto=' prepending with `'` will affect the current view
(e.g. limit to unread documents, limit to entries with notes, ..).
Sorting can be done with `S`, like in vifm.
Display style can be toggled to table with `T`.
Moved my old study library to the more descriptive emgs library
to differentiate from newly added studies under the academia
library.
Both can still be accessed through the main library.
Papis reload will now only rebuild the cache of the currently
active library by default. To rebuild the cache of all libraries
papis knows, simply supply the `--all` switch.
Papis show can now show output styled by python-rich if it
is in the environment. Otherwise falls back to normal
console printing.
Added more information to output (journal, volume, issue,
type, doi) but also added `-s` switch which returns to
old single-line behavior for copying to other programs.
Moved plugins into individual component module files which are
automatically required by lazy.nvim. Should make everything a tiny bit
more modular, or at least prepare the way for true modularity if I ever
have the time on my hands to ensure everything works with missing
modules.
Moved core settings into their own directory (`core`), and created a
`personal` folder which contains functions/plugins I wrote that do not
necessarily have to be their own imported plugin yet.
Finally, extended the utility functions a little, so we can detect if a
plugin exists and change e.g. key maps based on that (once again,
extending modularity a little more). Some simple attempts have been made
at that in the `mappings.lua` file, though it is nowhere near extensive
yet - most keymaps are still set regardless of plugin availability.
However, with this slimmer base to work off of, I feel more confident in
changing future things about this setup a little more ad-hoc without
having as many ripple repercussions as before.
