unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@lsi.nec.co.jp>
Cc: emacs-devel@gnu.org
Subject: Re: Major update just committed
Date: 26 May 2003 12:47:15 +0900	[thread overview]
Message-ID: <buo7k8ebc8s.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <5x3cj3x34e.fsf@kfs2.cua.dk>

I now see a approx. two-column wide strip of emacs' frame not being
redraw when a emacs window is raised over a window previously obscuring
part of the emacs X window.  It only seems to happen on the _right_
side of the exposed area.

E.g., if I have this:

    +----------------------+
    |                      |
    |      Emacs           |
    |                      |
    |   +--------------+   |
    |   |              |   |
    |   |  Other X app |   |
    |   |              |   |
    +---|              |---+
        |              |
        +--------------+

and raise the Emacs frame, I'll get this:

    +----------------------+
    |                      |
    |      Emacs           |
    |                      |
    |                 XX   |
    |                 XX   |
    |                 XX   |
    |                 XX   |
    +----------------------+
        |              |
        +--------------+

Where the `XX' area is not redrawn properly (it ends up blank).

The fact that the problem area is about two columns wide make me think
that it's somehow related to the fringe calculations.

-Miles
--
Occam's razor split hairs so well, I bought the whole argument!

  parent reply	other threads:[~2003-05-26  3:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-25  0:48 Major update just committed Kim F. Storm
2003-05-25  1:26 ` Juanma Barranquero
2003-05-25  8:23   ` David Ponce
2003-05-26  3:47 ` Miles Bader [this message]
2003-05-28  0:18   ` Kim F. Storm
2003-05-27 13:28 ` Kenichi Handa
2003-05-28  0:16   ` Kim F. Storm
2003-05-27 22:39     ` Stefan Monnier
2003-05-28  3:53       ` Eli Zaretskii
2003-05-28 23:58         ` Richard Stallman
2003-05-29  3:46           ` Eli Zaretskii
2003-05-29 13:45             ` Stefan Monnier
2003-05-29 17:15             ` Juanma Barranquero
2003-05-29 17:24               ` Stefan Monnier
2003-05-30  0:55                 ` Kim F. Storm
2003-05-30  0:48               ` Richard Stallman
2003-05-30  7:23                 ` Juanma Barranquero
2003-05-31 19:52                   ` Richard Stallman
2003-05-31 20:33                     ` Stefan Monnier
2003-06-01 12:58                       ` Jason Rumney
2003-06-01 15:51                       ` Eli Zaretskii
2003-06-04  8:54                       ` Richard Stallman
2003-06-01 15:24                     ` Juanma Barranquero
2003-06-01 20:11                       ` Jason Rumney
2003-06-01 15:49               ` Eli Zaretskii
2003-06-01 15:56                 ` Juanma Barranquero
2003-05-27 22:41     ` Juanma Barranquero
2003-05-27 23:03     ` Jason Rumney
2003-05-27 23:22     ` Kenichi Handa

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=buo7k8ebc8s.fsf@mcspd15.ucom.lsi.nec.co.jp \
    --to=miles@lsi.nec.co.jp \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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).