unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, lektu@terra.es
Subject: Re: Potential redisplay problem [Re: Recursive load of mule-util.elc]
Date: Fri, 15 Nov 2002 20:34:17 -0500	[thread overview]
Message-ID: <E18Crqj-00056g-00@fencepost.gnu.org> (raw)
In-Reply-To: <200211141259.VAA20001@etlken.m17n.org> (message from Kenichi Handa on Thu, 14 Nov 2002 21:59:49 +0900 (JST))

    I don't mean to do that in general, but to add such a
    suppressing code somewhere in this calling sequence:
    >     message_with_string -> message3 -> message3_nolog
    >	->  echo_area_display -> redisplay_mode_lines ->
    >	->  display_mode_lines -> display_mode_element

I think it would work to make this code

	  /* If the display update has been interrupted by pending
	     input, update mode lines in the frame.  Due to the
	     pending input, it might have been that redisplay hasn't
	     been called, so that mode lines above the echo area are
	     garbaged.  This looks odd, so we prevent it here.  */
	  if (!display_completed)
	    n = redisplay_mode_lines (FRAME_ROOT_WINDOW (f), 0);

bind redisplaying_p in the same way redisplay_internal does.

      reply	other threads:[~2002-11-16  1:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04  7:26 Recursive load of mule-util.elc Juanma Barranquero
2002-11-05 10:47 ` Juanma Barranquero
2002-11-06  1:07   ` Kenichi Handa
2002-11-06  7:44     ` Juanma Barranquero
2002-11-06 12:20     ` Juanma Barranquero
2002-11-06 13:02       ` Kenichi Handa
2002-11-07  1:46         ` Potential redisplay problem [Re: Recursive load of mule-util.elc] Kenichi Handa
2002-11-08 12:07           ` Richard Stallman
2002-11-13  7:36             ` Kenichi Handa
2002-11-14 12:16               ` Richard Stallman
2002-11-14 12:16               ` Richard Stallman
2002-11-14 12:59                 ` Kenichi Handa
2002-11-16  1:34                   ` Richard Stallman [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=E18Crqj-00056g-00@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lektu@terra.es \
    /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).