bug#12876: 24.3.50; DocView problem with cached files

[Tassilo Horn]

Stephen Berman <stephen.berman@gmx.net> writes:

>> the following patch fixes the issue for me, but I'm not sure if it's
>> the right thing to do.  Stefan, could you please check?
>>
>> Basically, the difference between finding a not yet converted doc and
>> a doc that's already cached is that in the former case
>> `doc-view-goto-page' runs with the selected window displaying the
>> doc's buffer.  AFAIKS, that's a must for the image-mode winprops
>> stuff to work, so in the latter case, the patch defers running
>> `doc-view-goto-page' a bit into the future when the window showing
>> the doc buffer is hopefully there.
>
> The patch fixes the problem for me, too; thanks.  However, the delay
> of 0.1 seconds results in the unconverted file being noticeable before
> the image is displayed.

Yes, but that's no big deal IMHO.  You'll see the raw source for a short
time also when the doc isn't cached already.

> I tried it with a 0.01 second delay and this makes the image appear
> practically instantly to me, i.e., I didn't see the unconverted
> source, and the paging still worked.  I don't know if this short a
> delay is always guaranteed to succeed.

It'll also work, but chances increase that the page-setting is deferred
another fraction again.  I tried to set the value so that it's not
inconvenient but at the same time shouldn't need to delay again on
slower systems.

Bye,
Tassilo