From: Eli Zaretskii <eliz@gnu.org>
To: Marcin Borkowski <mbork@mbork.pl>
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:23:21 +0200 [thread overview]
Message-ID: <83wprxcdwm.fsf@gnu.org> (raw)
In-Reply-To: <87twn188bf.fsf@mbork.pl> (message from Marcin Borkowski on Tue, 29 Dec 2015 18:37:40 +0100)
> From: Marcin Borkowski <mbork@mbork.pl>
> Cc: Emacs-devel@gnu.org
> Date: Tue, 29 Dec 2015 18:37:40 +0100
>
> > Because it needs to determine the new window-start which is a
> > window-full above or below the current one, without assuming that all
> > the lines have the same height in pixels. How do you do that in Lisp?
> > (The current implementation simulates display.)
>
> Interesting, though I know too little about Emacs internals to fully
> understand your answer. I thought it just does something like
>
> (save-excursion
> (other-buffer)
> (scroll-up))
>
> Why my (probably naïve) implementation won't work?
(You forget other-window-for-scrolling, but that's beside the point.)
How would that help? The guts are in scroll-up, which is in C (as all
the scrolling commands).
Or are you saying that the bug is in the other-buffer part, rather
than in the scrolling part?
> > Sounds like a bug that should be reported. Not sure if it's in core
> > Emacs or not, but please do report it with all the necessary details
> > to whatever the guilty parties are.
>
> Not Emacs core, you're right. I'll file a bug report.
Thanks.
next prev parent reply other threads:[~2015-12-29 18:23 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 [this message]
2015-12-29 18:44 ` Marcin Borkowski
2015-12-29 19:01 ` Eli Zaretskii
2015-12-29 19:41 ` Marcin Borkowski
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=83wprxcdwm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Emacs-devel@gnu.org \
--cc=mbork@mbork.pl \
/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).