The road to dropping xdvik

Matthew Saltzman mjs at clemson.edu
Thu Jan 28 01:16:07 UTC 2010


On Thu, 2010-01-28 at 01:47 +0200, Jussi Lehtola wrote: 
> On Wed, 2010-01-27 at 23:08 +0000, Jonathan Underwood wrote:
> > 2010/1/27 Orion Poplawski <orion at cora.nwra.com>:
> > > I suspect a lot of our users will be similarly annoyed.  This is one of
> > > those kinds of tools that "just works" and so people stick with it.
> > 
> > Well.. perhaps. OTOH people seem to have happily migrated from xpdf to
> > evince over time (or at least that's my perception).
> 
> What do you mean?
> 
> # yum -y install xpdf
> (clip)
> ---> Package xpdf.x86_64 1:3.02-15.fc12 set to be updated
> 
> xpdf is still there, so actually nothing brutal has yet happened in the
> case of xpdf. When xpdf *is* removed I'd expect cries of rage.

Indeed, there are several features of xpdf that evince doesn't yet
support.  Until it does, it turns out to be useless with emacs-auctex,
for one thing.

https://bugzilla.redhat.com/show_bug.cgi?id=451210

> 
> **
> 
> For PDFs I personally have used evince ever since it was introduced in
> Fedora. In the case of PDFs the wait for a page to load is just a second
> or so.
> 
> For PS (or EPS!) files, on the other hand, evince can be *really* slow
> in my experience. Often I just convert the files to PDF first with
> ps2pdf or epstopdf - if a file doesn't seem to open launching another
> terminal, converting the file to PDF and launching another evince
> process to view it is quicker to display than the original process that
> had been running all the time in the background.

-- 
                Matthew Saltzman

Clemson University Math Sciences
mjs AT clemson DOT edu
http://www.math.clemson.edu/~mjs


More information about the devel mailing list