unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, storm@cua.dk
Subject: Re: [miles@lsi.nec.co.jp: redisplay abort if GLYPH_DEBUG turned on]
Date: Thu, 06 Jan 2005 14:56:14 -0500	[thread overview]
Message-ID: <E1Cmdjy-0006iC-P9@fencepost.gnu.org> (raw)
In-Reply-To: <buo3bxfz3vm.fsf@mctpc71.ucom.lsi.nec.co.jp> (message from Miles Bader on Thu, 06 Jan 2005 11:29:49 +0900)

    > There are other places which set stop_charpos to 0, so
    > there is IT_CHARPOS <= stop_charpos is not an invariant.

    The thing that makes me nervous is that there seem to also be other
    similar xasserts, e.g. [xdisp.c:2727]:

It's good to be nervous when you see something like that.

Looking at the places that set stop_charpos to 0, I see that they
usually also set it->string to a string.  Here's one possible
exception in reseat_to_string,

  else
    {
      it->s = s;
      it->string = Qnil;

but it sets it->s instead.

The only other exception is the newly added code in set_iterator_to_next.
So I think that setting stop_charpos to 0 is not the right way to
do the job there.

  reply	other threads:[~2005-01-06 19:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Cm1td-0003LC-VL@fencepost.gnu.org>
     [not found] ` <m33bxfwxd8.fsf@kfs-l.imdomain.dk>
2005-01-06  2:29   ` [miles@lsi.nec.co.jp: redisplay abort if GLYPH_DEBUG turned on] Miles Bader
2005-01-06 19:56     ` Richard Stallman [this message]
2005-01-06 21:55     ` Kim F. Storm
2005-01-07 13:17       ` Kim F. Storm

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=E1Cmdjy-0006iC-P9@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=storm@cua.dk \
    /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).