unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Stephen Berman <Stephen.Berman@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: Contiguous redisplay of the menu and beeps
Date: Sat, 26 May 2007 16:49:51 +0200	[thread overview]
Message-ID: <4658490F.5070908@gmx.at> (raw)
In-Reply-To: <87hcpzekb6.fsf@escher.local.home>

 > That is, I get continuous beeping and Emacs consumes the CPU, but I
 > don't see menu redisplay.  And in fact, I can stop the beeping and CPU
 > consumption by clicking on clicking the SGML menu and toggling tag
 > visibility.  Clicking on the HTML menu stops the beeping but it
 > resumes when the menu is closed.  Clicking on the other menues does
 > not seem to stop the beeping.  I'm not sure these observations are
 > reliably reproducible.
 >
 > Steve Berman

What happens if you change `sgml-point-entered' to the following
non-sensical?  My Emacs consumes 100% CPU and won't react to C-g.
Occasionally I can see `my-count' going up though.

(defvar my-count 0)

(defun sgml-point-entered (x y)
   ;; Show preceding or following hidden tag, depending of cursor direction.
   (let ((inhibit-point-motion-hooks t)
	(tag-string
	 (save-excursion
	   ;; Strip properties, otherwise, the text is invisible.
	   (buffer-substring-no-properties
	    (point)
	    (if (or (and (> x y)
			 (not (eq (following-char) ?<)))
		    (and (< x y)
			 (eq (preceding-char) ?>)))
		(condition-case nil
		    (backward-list)
		  (error (progn (message "... %s" (setq my-count (1+ my-count)))
				(sit-for 1) (ding)
				(point))))
	      (condition-case nil
		  (forward-list)
		(error (progn (message "... %s" (setq my-count (1+ my-count)))
			      (sit-for 1) (ding)
			      (point)))))))))
     (unless (string-equal tag-string "")
       (message "Invisible tag: %s" tag-string))))

  reply	other threads:[~2007-05-26 14:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ulkfcxbvv.wl%miyoshi@meadowy.org>
     [not found] ` <465811AB.6080507@gmx.at>
2007-05-26 13:41   ` Contiguous redisplay of the menu and beeps martin rudalics
2007-05-26 14:12     ` Stephen Berman
2007-05-26 14:22       ` Stephen Berman
2007-05-26 14:49         ` martin rudalics [this message]
2007-05-26 15:19           ` Stephen Berman
2007-05-26 16:12             ` martin rudalics
2007-05-27 23:21 Richard Stallman
2007-05-28  0:56 ` YAMAMOTO Mitsuharu
2007-05-28  2:32   ` Chong Yidong
2007-05-28  3:11     ` YAMAMOTO Mitsuharu
2007-05-28  8:33       ` martin rudalics
2007-05-28  8:58         ` martin rudalics
2007-05-28  9:14           ` YAMAMOTO Mitsuharu
2007-05-28  9:42             ` martin rudalics
2007-05-28 10:09             ` martin rudalics
2007-05-28 12:49               ` Chong Yidong
2007-05-28 13:13                 ` martin rudalics
2007-05-28 14:11                   ` Chong Yidong
2007-05-29 23:38                 ` Davis Herring
2007-05-29  0:03     ` Richard Stallman

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=4658490F.5070908@gmx.at \
    --to=rudalics@gmx.at \
    --cc=Stephen.Berman@gmx.net \
    --cc=emacs-devel@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).