From: Juri Linkov <juri@jurta.org>
To: emacs-pretest-bug@gnu.org
Cc: Tassilo Horn <tassilo@member.fsf.org>
Subject: DocView: SPC doesn't go the the next page
Date: Fri, 04 Jan 2008 01:16:46 +0200 [thread overview]
Message-ID: <8763ya1plt.fsf@jurta.org> (raw)
In the latest version of doc-view.el, when the image height is greater
than the Emacs window's height, typing SPC (doc-view-scroll-up-or-next-page)
doesn't go to the next page. Instead, when if reaches the end of the current
page, it goes to the beginning of the current page.
--
Juri Linkov
http://www.jurta.org/emacs/
next reply other threads:[~2008-01-03 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 23:16 Juri Linkov [this message]
2008-01-04 8:30 ` DocView: SPC doesn't go the the next page Tassilo Horn
2008-01-04 9:54 ` Juri Linkov
2008-01-04 13:33 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8763ya1plt.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=tassilo@member.fsf.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).