From: Tassilo Horn <tassilo@member.fsf.org>
To: emacs-devel@gnu.org
Subject: Re: doc-view-current-slice only used internally
Date: Sat, 05 Jan 2008 18:47:30 +0100 [thread overview]
Message-ID: <87zlvk2mh9.fsf@member.fsf.org> (raw)
In-Reply-To: <m1JBBHF-002K4LC@rattlesnake.com> (Robert J. Chassell's message of "Sat, 5 Jan 2008 15:49:37 +0000 (UTC)")
"Robert J. Chassell" <bob@rattlesnake.com> writes:
Hi Robert,
> The cache is useful. Without it, that is to say, when you first start
> doc-view-mode, an `emacs -Q -D' instance says the DVI to PNG
> conversion is pdf/ps->png, which is obviously an error.
No, it's not. A dvi will be converted to pdf and that in turn is
converted to png. That's needed cause ghostview doesn't work with dvi
files.
> Also, it takes a minute to convert the first thirty pages. Put
> another way, it takes a very long time when your document has 173
> pages in it.
Yeah, since they need a 2-way conversion, dvi files take the longest
conversion time.
> xdvi takes less time than I can determine.
Well, xdvi can display dvi files natively, so there's no need to do a
time-consuming conversion before.
> Perhaps you can save time by checking whether xdvi exists on the
> computer and, if so, use it in Emacs.
Emacs cannot embed other windows.
> Incidently, when I have the cache and am starting a new instance of
> `emacs -Q -D', doc-view-mode seems to require that I go a page ahead
> to see the smaller slice
Yes, that is correct. The first image will be displayed before
doc-view-mode-hook is run.
Bye,
Tassilo
next prev parent reply other threads:[~2008-01-05 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 16:22 doc-view-current-slice only used internally Robert J. Chassell
2008-01-04 19:22 ` Tassilo Horn
2008-01-04 21:39 ` Robert J. Chassell
2008-01-04 22:26 ` Tassilo Horn
2008-01-05 15:49 ` Robert J. Chassell
2008-01-05 17:47 ` Tassilo Horn [this message]
2008-01-05 18:57 ` David Kastrup
2008-01-05 19:30 ` Tassilo Horn
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=87zlvk2mh9.fsf@member.fsf.org \
--to=tassilo@member.fsf.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.