From: Richard Stallman <rms@gnu.org>
Cc: quarl@quarl.org
Subject: Re: redisplay code + non-plain-text-only buffers + scroll-conservatively [Re: Bug: ruler-mode breaks scroll-conservatively (HEAD)]
Date: Thu, 02 Jan 2003 13:39:26 -0500 [thread overview]
Message-ID: <E18UAFa-0004Da-00@fencepost.gnu.org> (raw)
In-Reply-To: <20021231103426.CA1B.LEKTU@terra.es> (message from Juanma Barranquero on Tue, 31 Dec 2002 10:52:51 +0100)
Still, there's a difference between scrolling down a buffer with
partially visible lines and without. With full lines, if you maintain
<down> pressed, the scroll is totally smooth. With a partially-visible
last line, the scroll "jumps" slightly every now and then (at more-or-less
equally distributed intervals, apparently).
That is going to be quite hard to debug, since it can't be reproduced
and happens only occasionally in a series of many similar actions.
The only technique I can think of is to insert debugging log output
code in many places, and record all the output; then, when it fails,
go back and find the log output for that failure and see how it
differs from the usual log output.
I can't afford to do this myself--I am overloaded. Would someone else
like to do it?
The place to start putting in the debugging printouts is in various places
in the function try_scrolling.
prev parent reply other threads:[~2003-01-02 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15867.5338.229659.360718@quack.quarl.org>
[not found] ` <E18Sgcd-00078i-00@fencepost.gnu.org>
2002-12-30 0:52 ` redisplay code + non-plain-text-only buffers + scroll-conservatively [Re: Bug: ruler-mode breaks scroll-conservatively (HEAD)] quarl
2002-12-31 5:48 ` Richard Stallman
2002-12-31 9:52 ` Juanma Barranquero
2002-12-31 11:35 ` Karl Chen
2003-01-02 18:39 ` Richard Stallman [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=E18UAFa-0004Da-00@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=quarl@quarl.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).