[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: doc-view stuck on same image

From: harold . carr
Subject: Re: doc-view stuck on same image
Date: Thu, 10 Oct 2013 09:56:11 -0700

A little more info:

When I startup emacs with -Q, doc-view works fine.

Then, in the same -Q emacs process, I do

M-x load-theme

then it gets stuck on the last image I view - no matter what .pdf, .jpg,
etc., file I visit.

Does that happen for anyone else using load-theme and

GNU Emacs 24.3.1 (x86_64-apple-darwin11.4.2, NS apple-appkit-1138.51) of
2013-03-31 on


On Thu, Oct 10, 2013 at 7:44 AM, <address@hidden> wrote:

> -Q  makes it work fine.
> Looks like I will have do binary narrowing of my LARGE .emacs file to find
> out what piece is causing this.
> On Thu, Oct 10, 2013 at 2:10 AM, Tassilo Horn <address@hidden> wrote:
>> address@hidden writes:
>> Hi Harold,
>> >     GNU Emacs 24.3.1 (x86_64-apple-darwin11.4.2, NS
>> apple-appkit-1138.51)
>> > of 2013-03-31 on
>> >
>> > when I use doc-view (automatically) when visiting *.pdf, *.tiff, *.ps,
>> > etc., files it either:
>> >
>> > - keeps showing me the same image (no matter what page or file I visit)
>> >   - usual the image show in the *GNU Emacs* buffer
>> That's really strange.  I wonder how that can happen.  Or well, there's
>> a theoretical possibility that two different files with the same name
>> and accidentally identical md5sums are treated as identical by doc-view.
>> But that's really almost impossible, and it cannot happen if the files
>> have different names.
>> > - starts using HIGH CPU doing what?  - I finally just kill it
>> That might be the conversion form PDF (or whatever) to PNG images which
>> would be normal.  But that shouldn't be slower than with previous emacs
>> versions.  Quite contrary, if you have mupdf installed, it should be
>> much faster instead.
>> Or wait: if it was be the normal conversion process, then the high CPU
>> load would come from ghostscript, mudraw, libre/openoffice etc., but not
>> from the emacs process itself...
>> > It used to work fast and fine.  Unfortunately I do not know what I did
>> > differently (i.e., emacs version, config settings) when this started
>> > happening.
>> >
>> > Any ideas?
>> That's really hard to guess.  The very first thing you should try is to
>> start emacs with "emacs -Q" and then opening some PDF file.  If it works
>> then, something's broken with your configuration.
>> Bye,
>> Tassilo

reply via email to

[Prev in Thread] Current Thread [Next in Thread]