From: Tassilo Horn <tassilo@member.fsf.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 2549@emacsbugs.donarmstrong.com, Markus Triska <markus.triska@gmx.at>
Subject: bug#2549: 23.0.60; doc-view: scrolling other window wraps unexpectedly
Date: Tue, 03 Mar 2009 20:14:23 +0100 [thread overview]
Message-ID: <871vte1ks0.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <jwv8wnma7ar.fsf-monnier+emacsbugreports@gnu.org> (Stefan Monnier's message of "Tue, 03 Mar 2009 11:44:37 -0500")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> That's because `scroll-other-window' calls scroll-up/down in the
>> other window, but if the other window contains an doc-view buffer it
>> should ideally call image-scroll-up/down.
>
>> The only good solution I see is to define buffer local variables
>> `scroll-up-function' and `scroll-down-function' which are used by
>> `scroll-up' and `scroll-down' and then binding them appropriate in
>> each mode.
>
> Indeed, something like a hook seems necessary. I'd rather leave it as
> is for Emacs-23.1, tho. Makes me wonder: do we have a way to tag bugs
> as "post-23.1"?
We could abuse the "Version:" pseudo-header for that or create a new tag
for that. The latter seems more desirable, but I don't know how to
create a tag. Maybe they're created automagically? I'll try by sending
tags 2549 + post-23.1
to the control server address...
Bye,
Tassilo
next prev parent reply other threads:[~2009-03-03 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2246.1236045825.31690.bug-gnu-emacs@gnu.org>
2009-03-03 12:00 ` bug#2549: 23.0.60; doc-view: scrolling other window wraps unexpectedly Tassilo Horn
2009-03-03 16:44 ` Stefan Monnier
2009-03-03 19:14 ` Tassilo Horn [this message]
2009-03-04 1:16 ` Stefan Monnier
2009-03-04 12:44 ` martin rudalics
2009-03-03 1:39 Markus Triska
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=871vte1ks0.fsf@thinkpad.tsdh.de \
--to=tassilo@member.fsf.org \
--cc=2549@emacsbugs.donarmstrong.com \
--cc=markus.triska@gmx.at \
--cc=monnier@IRO.UMontreal.CA \
/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.