unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: npostavs@users.sourceforge.net
Cc: 24633@debbugs.gnu.org
Subject: bug#24633: highlight-region func using (window-hscroll) in :align-to spec can cause inf loop
Date: Sat, 22 Oct 2016 22:41:41 +0300	[thread overview]
Message-ID: <83inskp3wq.fsf@gnu.org> (raw)
In-Reply-To: <87y41grxox.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net)

> From: npostavs@users.sourceforge.net
> Cc: 24633@debbugs.gnu.org
> Date: Sat, 22 Oct 2016 15:27:42 -0400
> 
> I tried adding a counter in redisplay_internal, it prevents having a
> tight loop in C.  Actually, the behaviour becomes like the split window
> case: there is additional hscrolling each time the cursor blinks, but it
> can be interrupted with C-g.  That seems adequate behaviour to me, what
> do you think?

Did you see what happens when blink-cursor-mode is turned off?  (If
that's what you meant by "each time the cursor blinks; if not, what
caused it to blink?)

The patch looks OK to me, so if it gives better results than locking
up Emacs with the current code, let's push it to master.

> > Do you really think that a formal grammar, whether accurate/complete
> > or not, is a good way of describing a feature?
> 
> The formal grammar plus the informal description of what the parts mean
> seems a perfectly fine description for _this_ feature.

Not to me, not anywhere close to being fine.  For starters, Emacs Lisp
programmers don't have to be proficient in reading formal grammars.
But that's me.

Thanks.





  reply	other threads:[~2016-10-22 19:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07  1:01 bug#24633: highlight-region func using (window-hscroll) in :align-to spec can cause inf loop npostavs
2016-10-08 11:15 ` Eli Zaretskii
2016-10-08 17:17   ` npostavs
2016-10-08 18:01     ` Eli Zaretskii
2016-10-08 19:18       ` npostavs
2016-10-08 19:57         ` Eli Zaretskii
2016-10-09 12:29           ` npostavs
2016-10-09 12:42             ` Eli Zaretskii
2016-10-22 19:27               ` npostavs
2016-10-22 19:41                 ` Eli Zaretskii [this message]
2016-10-22 20:43                   ` npostavs

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=83inskp3wq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24633@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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).