Thanks, I guess I will be using the binary look approach from now on.
iBertus:
Yes I'm picky. I'm very easily annoyed by irritating things when it comes to applications. So I'm striving for perfection.
- Nov 20, 2017 Use the evil collection package, which has a special setup to use vim keybindings in pdf-tools. Although, you must take into consideration that you would have some issues with strange pdf blinking behavior. For fixing that, I mix the info I found here and here.
- IntelliJ IDEA Vim-like plugin. Irsii vim-mode.pl plugin. An Irssi script to emulate some of the vi (m) features for the Irssi inputline. BSD-like Perl An Irssi script to emulate some of the vi (m) features for the Irssi inputline. NetBeans IDE Vim-like plugin.
- Re: Good PDF reader. I'm liking a lot zathura: gtk, poppler and cairo are the only dependencies, vim-like keybindings and does remember where you left (with:bmark). Very fast, obviously.
apaige:
Bloted or not. When it comes to rendering pages, Acreread does it twice as fast as Xpdf. Xpdf start faster thou.
I did a simple test on startup time and jumping from page 1 -> 2 on a document. This is not very scientific, since there is a lot of variables. Had a few things running in the background.
The startuptest is done by loading the pdfreader with a pdf file from a terminal. It was no restart of the computer between the different readers, so the last ones might benefit from already loaded dependencies.
Jump from one page to the next is done with the reader in fullscreen and with the pdf page fit height. I did this mainly from page one to two. But the three last use preloading of the pages, so I had to jump fast down until I came down to a page that was not preloaded.
Custom keybindings for the qpdfview PDF reader. Contribute to nbeaver/qpdfview-shortcuts-config development by creating an account on GitHub.
Here is the file used.
The result.
[Solved] Synchronize PDF Reading ...
xpdf, startup: 6.4 sec, load page 1 -> 2: 4.0 sec
acroread, startup: 11.5 sec, load page 1 -> 2: 1.8 sec
epdefview, startup: 26.7 sec, load page: 2.2 sec
okular, startup: 13.5 sec, load page: 1.3 sec
evince, startup: 17.9 sec, load page: 1.1 sec
So, both Okular and Evince are very good readers. The only problem is the KDE/Gnome dependencies making them both slow starters. The second start will be fast since things already have been loaded. So one of them will be my preferred reader for now.
Cached
Last edited by orjanp (2008-11-11 14:36:51)