unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs-devel@gnu.org
Subject: Re: Is there any particular reason `scroll-other-window' is written in C and not in ELisp?
Date: Tue, 29 Dec 2015 20:41:00 +0100	[thread overview]
Message-ID: <87poxp82lv.fsf@mbork.pl> (raw)
In-Reply-To: <83twn1cc5k.fsf@gnu.org>



On 2015-12-29, at 20:01, Eli Zaretskii <eliz@gnu.org> wrote:

>> From: Marcin Borkowski <mbork@mbork.pl>
>> Cc: Emacs-devel@gnu.org
>> Date: Tue, 29 Dec 2015 19:44:21 +0100
>> 
>> Now that I think of it, I guess rewriting scroll-other-window in Elisp
>> wouldn't help a lot - I'd probably still have to advise them, or else
>> C-M-v should check what is bound to <next> and <prior> in the buffer to
>> be scrolled.  Does anyone have a better idea how to be able to scroll
>> a pdf in other window using C-M-v and C-M-S-v?
>
> It sounds like there has to be some entirely different command bound
> to C-M-v for what you want to happen.  The stock scrolling commands
> know nothing about the significance of the "next PDF page", so they
> cannot possibly do that for you.  They just bring more stuff from the
> buffer into view.

This made me think that it /might/ be a good idea to introduce
a (buffer-local) variable (or a pair of variables) which would point to
function(s) taking the role of scroll-up/scroll-down in "unusual"
buffers.  This might make sense with pdfs, but also (possibly) images
(and maybe something else, too - I imagine EMMS's buffer /might/ point
those to emms-next/emms-previous, for instance).

WDYT?

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University



      reply	other threads:[~2015-12-29 19:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-29  9:32 Is there any particular reason `scroll-other-window' is written in C and not in ELisp? Marcin Borkowski
2015-12-29 16:02 ` Eli Zaretskii
2015-12-29 17:37   ` Marcin Borkowski
2015-12-29 18:23     ` Eli Zaretskii
2015-12-29 18:44       ` Marcin Borkowski
2015-12-29 19:01         ` Eli Zaretskii
2015-12-29 19:41           ` Marcin Borkowski [this message]

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=87poxp82lv.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=Emacs-devel@gnu.org \
    --cc=eliz@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 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).