Kavita VS fzf

Browse the Issue Tracker: Visit our bug tracker @ https://github.com/Kareadita/Kavita/issues to find a list of open issues tagged specifically for the Bug Bash. You'll find a variety of tasks, from beginner-friendly to advanced.

#! /bin/bash installFolder="/opt/Kavita" # defines the folder where Kavita is installed backupFolder="/opt/KavitaBackup" # defines the backup folder for kavita kavitaUser="kavita" # defines the kavita service user kavitaGroup="kavita" # defines the kavita service group architecture="kavita-linux-x64.tar.gz" # options are: # kavita-linux-x64.tar.gz # kavita-linux-arm.tar.gz # kavita-linux-arm64.tar.gz if [ ! -d $installFolder ] then echo "KAVITA FOLDER IS MISSING!!" exit 1 fi cd /tmp if [ -r $architecture ] then echo "Kavita already present - extracting now!" tar -xzf $architecture else echo "Downloading latest Kavita from GitHub" wget https://github.com/Kareadita/Kavita/releases/latest/download/$architecture echo "extracting now!" tar -xzf $architecture fi if [ ! -d Kavita ] then echo "Something went wrong downloading or extracting" exit 1 fi echo "Stopping Kavita service" systemctl stop kavita.service if [ -d $backupFolder ] then echo "Deleting old KavitaBackup" rm -r $backupFolder fi echo "Creating new Kavita backup" cp -r $installFolder/config $backupFolder echo "Deleting Kavita" rm -r $installFolder echo "Installing new Kavita" cp -r /tmp/Kavita $installFolder echo "Deleting default config" rm -r $installFolder/config echo "Moving old config into install folder" cp -r $backupFolder $installFolder/config echo "CHOWN Kavita folder to kavita user and group" chown -R $kavitaUser:$kavitaGroup $installFolder echo "Make Kavita executable" chmod +x $installFolder/Kavita echo "Launch Kavita" systemctl start kavita.service echo "Cleaning up downloaded files" rm -r Kavita rm $architecture echo "Update process finished :)"

--2023-09-19 18:28:27-- https://github.com/Kareadita/Kavita/releases/download/v0.7.1.4/kavita-linux-arm64.tar.gz

Hey, Kavita creator here and noticed you don't have any mentions of Kavita for epub readers. Kavita is not a Calibre replacement, but has a built-in epub/pdf reader along with some series-based organization.

https://www.kavitareader.com/

The full release can be found here.

In addition, I think bash's `operate-and-get-next` can be very helpful. When you go back through your shell history, you can hit Ctrl+o instead of enter and it will execute the command then put the next one in your history on the command line, and keep track of where you are in your history. This way, you can rerun a bunch of commands by going to the first one and Ctrl+o till you are done. And you can edit those commands and hit Ctrl+o and still go to the next previously run command.

Note: fzf's history search feature breaks this. https://github.com/junegunn/fzf/issues/2399

fzf : https://github.com/junegunn/fzf

Those are the most used aliases in my gitconfig.

"git fza" shows a list of modified/new files in an fzf window, and you can select each file with tab plus arrow keys. When you hit enter, those files are fed into "git add". Needs fzf: https://github.com/junegunn/fzf

"git gone" removes local branches that don't exist on the remote.

"git root" prints out the root of the repo. You can alias it to "cd $(git root)", and zip back to the repo root from a deep directory structure. This one is less useful now for me since I started using zoxide to jump around. https://github.com/ajeetdsouza/zoxide

> my history is so noisy I had to find another way

The fzf search syntax can help, if you become familiar with it. It is also supported in atuin [2].

[1]: https://github.com/junegunn/fzf#search-syntax

[2]: https://docs.atuin.sh/configuration/config/#fuzzy-search-syn...

You call it with `n` and get an interactive fuzzy search for your directories. If you do `n ` instead, it’ll start the find with `` already filled in (and if there’s only one match, jump to it directly). The `ls` is optional but I find that I like having the contents visible as soon as I change a directory.

I’m also including iCloud Drive but excluding the Library directory as that is too noisy. I have a separate `nl` function which searches just inside `~/Library` for when I need it, as well as other specialised `n` functions that search inside specific places that I need a lot.

¹ https://github.com/sharkdp/fd

² https://github.com/junegunn/fzf

View on GitHub

I do find the history pager stuff interesting, but ultimately not of tremendous use for me. I rebound all my history search stuff to use fzf[1] (via a fish plugin for such[2]), and so haven't been aware of the issues

[1] https://github.com/junegunn/fzf

[2] https://github.com/PatrickF1/fzf.fish

You can also use fzf with ripgrep to great effect:

[1]: https://github.com/junegunn/fzf/blob/master/ADVANCED.md#usin...