From: Lennart Borgman <lennart.borgman@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 6343@debbugs.gnu.org, Chong Yidong <cyd@stupidchicken.com>,
Dan Nicolaescu <dann@ics.uci.edu>
Subject: bug#6343: Log-edit font lock changes lead to loop
Date: Fri, 4 Jun 2010 12:34:15 +0200 [thread overview]
Message-ID: <AANLkTim1o-Jpu6vU9pY2OR8_b_B3i-qK1GK9ttZXmDPR@mail.gmail.com> (raw)
In-Reply-To: <AANLkTiloRfpRt_lLLXw0Qntq4RQ4Xpcz07yA--y_DwAv@mail.gmail.com>
On Fri, Jun 4, 2010 at 12:15 PM, Juanma Barranquero <lekktu@gmail.com> wrote:
> On Fri, Jun 4, 2010 at 04:12, Lennart Borgman <lennart.borgman@gmail.com> wrote:
>
>> A little bit off-topic: you mean you can't even stop with C-g?
>
> C-g acts weird. It stops, sort of, but then moving around makes Emacs
> loop again.
I did not notice that it stops first. Strange.
>> How do you normally handle that? (I put some limit on all font lock
>> loops in my code ... ;-) )
>
> You'll have to be a bit more specific.
I just do something like this in case I make a stupid error somewhere:
(defsubst visual-indent-while (limit counter where)
(let ((count (symbol-value counter)))
(if (= count limit)
(progn
(message "Reached (while limit=%s, where=%s)" limit where)
nil)
(set counter (1+ count)))))
(while (and (visual-indent-while 200 'n-while
"visual-indent-jit-lock-fun")
(< (point) bound)) ;; Max bound = (point-max)
next prev parent reply other threads:[~2010-06-04 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 17:17 bug#6343: Log-edit font lock changes lead to loop Chong Yidong
2010-06-03 17:36 ` Dan Nicolaescu
2010-06-04 1:40 ` Juanma Barranquero
2010-06-04 2:12 ` Lennart Borgman
2010-06-04 10:15 ` Juanma Barranquero
2010-06-04 10:34 ` Lennart Borgman [this message]
2011-07-12 8:10 ` Glenn Morris
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=AANLkTim1o-Jpu6vU9pY2OR8_b_B3i-qK1GK9ttZXmDPR@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=6343@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=dann@ics.uci.edu \
--cc=lekktu@gmail.com \
/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.