From: etosan <etosan@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package Request: llpp - saner pdf viewer
Date: Fri, 26 Mar 2021 20:46:10 +0100 [thread overview]
Message-ID: <20210326194610.kD54ommdmoavmfKZQJyFwK3D0QTY3HaSwsJ44t3UorA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29676@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]
New comment by etosan on void-packages repository
https://github.com/void-linux/void-packages/issues/29676#issuecomment-808470988
Comment:
@ericonr
> You might want to try zathura as a PDF viewer...
I remember trying `zathura` around 5+ years ago and it was very slow, quite heavy and quite cumbersome (nothing against it I am just not a fan). I am okay with few vimmy commands, but I am not really a friend with heavy vimmyness (if I remember correctly, `zathura` was very vimmy).
`mupdf` on the other hand is very lean, fast and light (I would say it is `mplayer` of pdf viewers). But doing extended reading sessions in it is getting pretty hard on me, as as I am getting older the pageflips are desorienting me too much.
Fortunately, then I found `llpp` and it was love at first sight. It has exactly the features I need and I care about (a lot), that no other pdf viewer provides (if I am not mistaken), so if `mupdf` is `mplayer`, `llpp` is `mpv` of pdf viewers. I don't see zathura as useful in my setup.
@eli-schwartz: yes I have my own build installed to /usr/local, but I requested this here, as it would allow me to get rid of the minimal maintenance it needs. It would perhaps help others as well as it did for me.
I have no clue how OCaml packaging, compiling and system interaction with libraries works, so that is why I have no idea, what it would entail, to have it as proper package.
Is that such a problem that mupdf is amalgammated into it statically?
next prev parent reply other threads:[~2021-03-26 19:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 12:57 [ISSUE] " etosan
2021-03-23 1:34 ` mattheusroxas
2021-03-26 19:46 ` etosan [this message]
2021-03-26 21:18 ` calibius
2021-03-26 21:22 ` calibius
2021-03-28 1:22 ` etosan
2021-03-28 15:54 ` calibius
2021-04-03 16:06 ` etosan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210326194610.kD54ommdmoavmfKZQJyFwK3D0QTY3HaSwsJ44t3UorA@z \
--to=etosan@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).