From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 18923@debbugs.gnu.org, esabof@gmail.com
Subject: bug#18923: Alternative scrolling model
Date: Mon, 03 Nov 2014 18:03:32 +0200 [thread overview]
Message-ID: <83r3xkw9t7.fsf@gnu.org> (raw)
In-Reply-To: <jwv38a12er7.fsf-monnier+emacsbugs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Sun, 02 Nov 2014 21:35:44 -0500
> Cc: 18923@debbugs.gnu.org
>
> >> BTW, have you looked at the C code of scroll-up/down at all?
> >> I'm not familiar with it, but it does do pixelwise scrolling to some
> >> extent as well (tho IIUC only for really tall lines such as those with
> >> images), so I'm curious to know exactly how the two compare.
> > I have tried different settings, but they haven't quite worked for me.
> > But I definitely need to become familiar with the existing
> > implementation.
>
> I don't think the behavior you're looking for can be obtained from the
> current C code, indeed, but maybe the needed changes are limited.
The current implementation only uses vscroll for partially visible
screen lines (a.k.a. "glyph rows"). This is by design (and consistent
with what line-move does), but we can decide to change that, if that's
what people want.
next prev parent reply other threads:[~2014-11-03 16:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 1:15 bug#18923: Alternative scrolling model E Sabof
[not found] ` <jwv61ey5qfb.fsf-monnier+emacsbugs@gnu.org>
[not found] ` <87vbmy9wdx.fsf@gmail.com>
2014-11-02 2:31 ` E Sabof
2014-11-02 15:16 ` Eli Zaretskii
2014-11-02 18:25 ` E Sabof
2014-11-02 18:36 ` Eli Zaretskii
[not found] ` <jwvioiy416g.fsf-monnier+emacsbugs@gnu.org>
[not found] ` <87sii1ahy9.fsf@gmail.com>
[not found] ` <jwvppd538tu.fsf-monnier+emacsbugs@gnu.org>
2014-11-02 23:10 ` E Sabof
2014-11-03 2:35 ` Stefan Monnier
2014-11-03 16:03 ` Eli Zaretskii [this message]
2014-11-03 19:02 ` E Sabof
2014-11-02 15:14 ` Eli Zaretskii
2014-11-02 15:56 ` Stefan Monnier
2014-11-02 16:06 ` Eli Zaretskii
2014-11-02 16:21 ` E Sabof
2014-11-02 16:31 ` Eli Zaretskii
2014-11-02 17:43 ` E Sabof
2014-11-02 18:22 ` Eli Zaretskii
2014-11-02 19:09 ` E Sabof
2014-11-02 19:29 ` Eli Zaretskii
2014-11-03 3:45 ` Eli Zaretskii
2019-11-04 9:14 ` Stefan Kangas
2022-04-22 12:16 ` Lars Ingebrigtsen
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=83r3xkw9t7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18923@debbugs.gnu.org \
--cc=esabof@gmail.com \
--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 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).