From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: inappropriate whole-frame flicker Date: Thu, 28 Aug 2003 15:17:37 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <20030828191737.GA23756@fencepost> References: <86brugya92.fsf@gerd.free-bsd.org> <861xvayk75.fsf@gerd.free-bsd.org> <8665klr8fe.fsf@gerd.free-bsd.org> <861xv7c94c.fsf@gerd.free-bsd.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1062098952 7150 80.91.224.253 (28 Aug 2003 19:29:12 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 28 Aug 2003 19:29:12 +0000 (UTC) Cc: Gerd Moellmann , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Thu Aug 28 21:29:10 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19sSSE-0000sT-00 for ; Thu, 28 Aug 2003 21:29:10 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 19sSZF-0005oc-00 for ; Thu, 28 Aug 2003 21:36:25 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.22) id 19sSNW-0003eZ-9N for emacs-devel@quimby.gnus.org; Thu, 28 Aug 2003 15:24:18 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.22) id 19sSLJ-0001h2-Ss for emacs-devel@gnu.org; Thu, 28 Aug 2003 15:22:01 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.22) id 19sSKy-0001BS-DX for emacs-devel@gnu.org; Thu, 28 Aug 2003 15:21:45 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.22) id 19sSKj-0000ok-Jq for emacs-devel@gnu.org; Thu, 28 Aug 2003 15:21:25 -0400 Original-Received: from miles by fencepost.gnu.org with local (Exim 4.20) id 19sSH3-0006Rc-LY; Thu, 28 Aug 2003 15:17:37 -0400 Original-To: Richard Stallman Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i Blat: Foop X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:16178 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:16178 On Thu, Aug 28, 2003 at 12:53:06PM -0400, Richard Stallman wrote: > We could also use a macro SET_GLYPH_FIELD (fieldname, value) which would > normally set the field using the standard place to find the glyph. But > when DEBUG, there would be two copies of the glyph, one initialized to all > 0s and one initialized to all 1s. Then SET_GLYPH_FIELD would set the > specified field in both glyphs. If the two glyphs are not identical, some > field was not set. Please don't do this now (if ever). That would uglify the code enormously, as well as causing many patching conflicts for out-of-tree code involving redisplay. Since the glyph stuff wasn't the cause of the problems I was seeing, there doesn't seem to be any urgency to making this particular aspect of glyph debugging easier. -Miles -- [|nurgle|] ddt- demonic? so quake will have an evil kinda setting? one that will make every christian in the world foamm at the mouth? [iddt] nurg, that's the goal