unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Yuri D'Elia <wavexx@thregr.org>
Cc: 24109@debbugs.gnu.org, djcb@djcbsoftware.nl,
	Christophe.Troestler@umons.ac.be
Subject: bug#24109: 24.5; Long lines in message mode make Emacs irresponsive
Date: Sat, 01 Oct 2016 20:47:00 +0300	[thread overview]
Message-ID: <83a8eoklm3.fsf@gnu.org> (raw)
In-Reply-To: <8737kgxaf0.fsf@wavexx.thregr.org> (message from Yuri D'Elia on Sat, 01 Oct 2016 19:10:27 +0200)

> From: Yuri D'Elia <wavexx@thregr.org>
> Cc: 24109@debbugs.gnu.org, djcb@djcbsoftware.nl, Christophe.Troestler@umons.ac.be
> Date: Sat, 01 Oct 2016 19:10:27 +0200
> 
> On Thu, Jan 01 1970, Yuri D'Elia <wavexx@thregr.org> wrote:
> >> What are your values of hscroll-step and hscroll-margin?
> 
> hscroll-step 0
> hscroll-margin 5
> 
> (default values)
> 
> > In addition to the above, here's one more: when hscroll_window_tree is
> > called with w->hscroll already non-zero (i.e. after the display engine
> > scrolls the window to bring point into the view), how come it tries
> > again to hscroll the window?  The complicated condition that starts at
> > line 12993 is supposed to yield false in that case, because the X
> > coordinate of the cursor, stored in w->cursor.x, is now supposed to be
> > between the left and the right hscroll margins.  Why isn't that
> > happening in your case?
> >
> > Some values that might help understand the answer to the above are:
> >
> >   in C:
> >     w->cursor
> >     w->min_hscroll
> >   in Lisp:
> >     hscroll-step
> >     hscroll-margin
> 
> It took me a while to sit down on this issue again.

Thanks, I hope you will be able to answer the rest of the questions
above, so I could continue looking into this problem.

> I noticed one thing while trying to restrict the problem: setting
> auto-hscroll-mode to nil, an error is shown in the *Messages* buffer
> instead of entering an infinite loop:
> 
> previous-line: Beginning of buffer

Could be related.  previous-line signals this error whenever its
subroutines report that point moved zero lines (more accurately, less
lines than they were asked to move).  It doesn't really check if it
hit BOB.

> while not moving the cursor at all on the first invocation, but working
> on the second. If something is off there, it might as well be trigger
> horizontal scrolling and thus conflict with the current goal column.

Sorry, I don't understand what the last sentence tries to say.

Thanks.





  reply	other threads:[~2016-10-01 17:47 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29 11:36 bug#24109: 24.5; Long lines in message mode make Emacs irresponsive Christophe Troestler
2016-07-30  7:07 ` Eli Zaretskii
2016-07-30 12:38   ` Christophe Troestler
2016-07-30 14:52     ` Clément Pit--Claudel
2016-07-30 15:55     ` Eli Zaretskii
2016-07-30 17:01       ` martin rudalics
2016-07-30 17:13         ` Eli Zaretskii
2016-07-30 17:30           ` martin rudalics
2016-07-30 18:02             ` Eli Zaretskii
2016-07-30 18:30               ` John Mastro
2016-07-30 18:48                 ` Eli Zaretskii
2016-07-30 19:22                 ` Dirk-Jan C. Binnema
2016-08-30 12:38 ` Yuri D'Elia
2016-08-30 12:45   ` Yuri D'Elia
2016-08-30 15:29   ` Eli Zaretskii
2016-08-30 15:51     ` Yuri D'Elia
2016-08-30 16:25       ` Eli Zaretskii
2016-08-31  9:15         ` Yuri D'Elia
2016-08-31 14:37           ` Eli Zaretskii
2016-08-31 15:51             ` Yuri D'Elia
2016-08-31 16:12               ` Eli Zaretskii
2016-08-31 16:49                 ` Yuri D'Elia
2016-09-01  2:35                   ` Eli Zaretskii
2016-09-01 14:30                     ` Eli Zaretskii
2016-09-01 14:39                       ` Yuri D'Elia
2016-09-01 14:48                         ` Yuri D'Elia
2016-09-01 15:18                           ` Eli Zaretskii
2016-09-01 15:37                             ` Yuri D'Elia
2016-09-01 16:00                               ` Eli Zaretskii
2016-09-03 13:25                                 ` Eli Zaretskii
     [not found]                       ` <28e7ddc58bcfeec0@fake-msgid>
2016-10-01 17:10                         ` Yuri D'Elia
2016-10-01 17:47                           ` Eli Zaretskii [this message]
2016-10-01 18:25                           ` Yuri D'Elia
2016-10-02  7:09                             ` Eli Zaretskii
2016-10-04  7:16                               ` Yuri D'Elia
2016-10-04  7:56                                 ` Eli Zaretskii
2016-10-08  7:55                               ` Eli Zaretskii
2016-10-08 15:27                                 ` Yuri D'Elia
2016-10-08 15:38                                   ` Eli Zaretskii
2016-10-08 15:42                                     ` Yuri D'Elia
2016-10-09 19:21                                   ` Christophe Troestler
2016-10-10  6:08                                     ` Eli Zaretskii

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=83a8eoklm3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24109@debbugs.gnu.org \
    --cc=Christophe.Troestler@umons.ac.be \
    --cc=djcb@djcbsoftware.nl \
    --cc=wavexx@thregr.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).