all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: kelly@prtime.org, 19060@debbugs.gnu.org
Subject: bug#19060: [FIX INCLUDED] Off-by-one-line scrolling bug in	window_scroll_pixel_based
Date: Sat, 15 Nov 2014 15:05:02 +0200	[thread overview]
Message-ID: <83d28ofwch.fsf@gnu.org> (raw)
In-Reply-To: <5467433F.4020906@gmx.at>

> Date: Sat, 15 Nov 2014 13:12:47 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: kelly@prtime.org, 19060@debbugs.gnu.org
> 
> First of all I'd need to understand the bug itself.  Do we assume that
> scrolling down is "correct" in some sense or does the bug manifest
> itself there already?  Does scrolling up always move to the line before
> the "previously established as correct" one or to the line after it?
> (I'm asking because I cannot reproduce the problem with Kelly Dean's
> pgup/pgdn recipe.)

Kelly, please help Martin reproduce the problem.  Perhaps you need to
provide more details, like maybe the file you used and the geometry of
the frame needed to see the issue.





  reply	other threads:[~2014-11-15 13:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <emacs-mail-is-unusable-4@[87.69.4.28]>
2014-11-15  9:27 ` bug#19060: [FIX INCLUDED] Off-by-one-line scrolling bug in window_scroll_pixel_based Eli Zaretskii
2014-11-15 11:13   ` martin rudalics
2014-11-15 11:17     ` Eli Zaretskii
2014-11-15 12:12       ` martin rudalics
2014-11-15 13:05         ` Eli Zaretskii [this message]
2014-11-15 13:29           ` martin rudalics
2014-11-15 13:47             ` Eli Zaretskii
2014-11-15 14:32               ` martin rudalics
2014-11-15 17:06                 ` Eli Zaretskii
     [not found] <emacs-mail-is-unusable-4>
2014-11-15 14:10 ` Angelo Graziosi
2014-11-15 14:33   ` martin rudalics
2014-11-15 17:18     ` Angelo Graziosi
2014-11-16 11:37       ` martin rudalics
2014-11-15  6:57 Kelly Dean

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=83d28ofwch.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=19060@debbugs.gnu.org \
    --cc=kelly@prtime.org \
    --cc=rudalics@gmx.at \
    /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.