From: Miles Bader <miles@gnu.org>
Cc: Gerd Moellmann <gerd.moellmann@t-online.de>, emacs-devel@gnu.org
Subject: Re: inappropriate whole-frame flicker
Date: Thu, 28 Aug 2003 15:17:37 -0400 [thread overview]
Message-ID: <20030828191737.GA23756@fencepost> (raw)
In-Reply-To: <E19sQ1C-00020r-AU@fencepost.gnu.org>
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
prev parent reply other threads:[~2003-08-28 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 9:31 inappropriate whole-frame flicker Miles Bader
2003-08-22 4:53 ` Miles Bader
[not found] ` <E19qPZe-0001gV-Ey@fencepost.gnu.org>
[not found] ` <86brugya92.fsf@gerd.free-bsd.org>
[not found] ` <E19qz9g-0000OF-Gs@fencepost.gnu.org>
[not found] ` <861xvayk75.fsf@gerd.free-bsd.org>
[not found] ` <E19rJ92-0003T9-Iq@fencepost.gnu.org>
[not found] ` <8665klr8fe.fsf@gerd.free-bsd.org>
[not found] ` <E19s3Lw-0004zB-JA@fencepost.gnu.org>
[not found] ` <861xv7c94c.fsf@gerd.free-bsd.org>
2003-08-28 16:53 ` Richard Stallman
2003-08-28 17:42 ` Gerd Moellmann
2003-08-28 19:17 ` Miles Bader [this message]
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=20030828191737.GA23756@fencepost \
--to=miles@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@t-online.de \
/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).