unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dima Kogan <dima@secretsauce.net>
To: 14567@debbugs.gnu.org
Subject: bug#14567: These changes sometimes break plain text navigation
Date: Sat, 06 Jul 2013 02:02:16 -0700	[thread overview]
Message-ID: <87r4fc9i3r.fsf@secretsauce.net> (raw)
In-Reply-To: <CAPcXcF0vncdwK6tp7FtnpEJRftPOWYr89HcH68g4CysQem=ZGg@mail.gmail.com>

Hi. I'm seeing the patches meant to address this bug break plain-text
scrolling. I'm reporting this new issue here, since it seems on-topic.
I'm running a close-to-HEAD emacs on a Debian box. The most recent
change to simple.el is this:

http://git.savannah.gnu.org/cgit/emacs.git/commit/lisp/simple.el?id=a7484019a30de380087389ccc8e5b0d0b8dae290

I'm observing that under some specific conditions (ones that my .emacs
just happens to hit) C-f can get stuck scrolling text instead of going
to the next line. To make the bug happen, I do this:

1. Load a text file. This is plain ASCII. No images or unicode or
   anything interesting. A nice test case is the output of 'seq 1000'

2. Press C-f repeatedly until the point reaches the bottom of the
   screen; this works fine

3. When at the bottom of the screen C-f scrolls the text one line up,
   while keeping the point where it was in the buffer. Now the point
   gets stuck, and subsequent C-f/C-b just scroll the screen; the point
   is stuck.


The bug requires particular .emacs settings. I wittled it down to this:

(custom-set-variables
 '(default-frame-alist
    '((font . "-adobe-courier-medium-r-normal--14-100-100-100-m-90-iso8859-1")))
 '(inhibit-startup-screen t))

(global-hl-line-mode)


The inhibit-startup-screen is there to be nicer; may not be required for
the bug. The (global-hl-line-mode) is significant. The bug doesn't
happen without it. That font is significant also. Other fonts seem to
work without the bug. I suspect the window sizes are significant as
well. I can see the bug if I launch 'emacs -geometry 30x30'. The
width/height of the emacs window as reported by xwininfo is then
308x455.

This is 100% reproducible for me. I suspect it may not be so for others.
Let me know if I should run any specific tests to get to the bottom of
this.

Thanks





  parent reply	other threads:[~2013-07-06  9:02 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06 12:17 bug#14567: Scrolling of large images Thomas Wiecki
2013-06-06 16:42 ` Eli Zaretskii
2013-06-06 17:16   ` Thomas Wiecki
2013-06-06 17:32     ` Eli Zaretskii
2013-06-08 14:19       ` Eli Zaretskii
2013-06-08 15:52         ` Thomas Wiecki
2013-06-08 16:49           ` Eli Zaretskii
2013-06-08 17:51             ` Thomas Wiecki
2013-06-08 18:44               ` Eli Zaretskii
2013-06-08 21:39                 ` Thomas Wiecki
2013-06-09  2:42                   ` Eli Zaretskii
2013-06-09  9:27                     ` Vitalie Spinu
2013-06-11 20:14                     ` David Engster
2013-06-15  8:23                       ` Eli Zaretskii
2013-06-15  9:02                         ` David Engster
2013-06-15  9:39                           ` Eli Zaretskii
2013-06-15 10:08                             ` David Engster
2013-06-15 11:13                               ` Thierry Volpiatto
2013-06-15 11:26                                 ` Eli Zaretskii
2013-06-15 12:41                                   ` Eli Zaretskii
2013-06-16  5:33                                     ` Thierry Volpiatto
2013-06-16  6:18                                       ` Thierry Volpiatto
2013-06-16 16:24                                         ` Eli Zaretskii
2013-06-17  4:57                                           ` Thierry Volpiatto
2013-06-17 15:14                                             ` Eli Zaretskii
2013-06-18 11:35                                               ` Thierry Volpiatto
2013-06-18 16:13                                                 ` Eli Zaretskii
2013-06-19  6:43                                                   ` Thierry Volpiatto
2013-07-06  9:02 ` Dima Kogan [this message]
2013-07-06 11:02   ` bug#14567: These changes sometimes break plain text navigation Eli Zaretskii
2013-07-06 16:14     ` Dima Kogan
2013-07-06 17:41       ` Eli Zaretskii
2013-07-06 21:51         ` Dima Kogan
2013-07-07  2:48           ` Eli Zaretskii
2013-07-07  4:46             ` Dima Kogan
2013-07-07 15:51               ` Eli Zaretskii
2013-07-07 18:57                 ` Dima Kogan
2013-07-08 17:35                   ` Eli Zaretskii
2013-07-08 23:42                     ` Dima Kogan
2013-07-09 17:00                       ` bug#14598: " Eli Zaretskii
2013-07-10  9:30                         ` Stephen Berman
2013-07-10 16:27                           ` Eli Zaretskii
2013-07-10 21:33                             ` Stephen Berman

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=87r4fc9i3r.fsf@secretsauce.net \
    --to=dima@secretsauce.net \
    --cc=14567@debbugs.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).