3 ms·
My solution to this has been to export the library as a bibtex file, which is a built in feature of Calibre, and then use ivy-bibtex (could just as easily use h
by vcxy 7y ago
My solution to this has been to export the library as a bibtex file, which is a built in feature of Calibre, and then use ivy-bibtex (could just as easily use helm-bibtex) to search the library. You need to make sure the file path is part of your bibtex export, but this is easily done. Also make sure you export tags.
- michaelmrose 7y agoSounds kind of manual compared to what I do now which is wrap calibredb in a script and narrow if needed via rofi. https://github.com/davatorium/rofi https://github.com/davatorium/rofi Presumably would be about as easy to do in elisp. A call to calibredb in a library of thousands of books on ssd is only 1/3 -> 1/2 a second
- vcxy 7y agoIt is a little more manual, but I think the end result is a little faster during use. This half second delay you mention doesn't happen with my library of over a thousand books. If I had something more automatic, I'd still want to be able to use bibtex. I like having the same interface for reading and citing, as well as the same for both reading books and reading papers. I bet there is a command line way to export a bibtex library, so it could be automated in elisp. It takes seconds though, and I only do it a few times a month. Doesn't matter though, I settled on this workflow because I was already using bibtex regularly for papers. Probably makes less sense if you aren't already happy with bibtex.