unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <117@emacsbugs.donarmstrong.com>, "'Jason Rumney'" <jasonr@gnu.org>
Subject: bug#117: bug 117: messed up frame parameters
Date: Wed, 27 Aug 2008 09:41:15 -0700	[thread overview]
Message-ID: <000c01c90863$b952b6c0$c2b22382@us.oracle.com> (raw)
In-Reply-To: <001401c8f4ec$471448b0$0200a8c0@us.oracle.com>

> From: Drew Adams Sent: Saturday, August 02, 2008 3:08 PM
> > > [Also, I still see the problem that a frame's text will 
> > > often become blanked out partially or completely and remain
> > > that way. I must select the frame and do `C-l' to get the
> > > text back. I assume that this is a general problem that has
> > > already been reported.]
> > 
> > A bad assumption. You appear to be the only one with this problem.
> 
> Oh, well, in that case the recipe is the same as for bug #117. 
> 
> You're right that I don't see the problem with just emacs -Q 
> (there is only a tiny delay before a frame gets repainted,
> if you move another frame over part of
> it temporarily etc).
> 
> What I see with oneonone.el is that a frame can remain 
> forever blanked out, until I go to it and do C-l. The blank
> part can be from from other window mgr window having covered
> part of the frame. But I think it can also happen without
> having been covered by another w-m window. If you try the 
> recipe I sent, you will soon enough see the problem. It might
> also happen more if there are more
> apps open (not sure) - e.g. multiple copies of Emacs.

In the pretest (22.2.90), all of the symptoms I reported previously (multiple
frame parameters, display problems) for this bug seem to have been taken care
of. 

Thanks very much. Dunno if this bug report helped at all, but anyway, thanks.







  reply	other threads:[~2008-08-27 16:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08 15:02 bug#117: bug 117: messed up frame parameters Drew Adams
2008-07-08 20:54 ` Jason Rumney
2008-07-09 15:27   ` Drew Adams
2008-08-02 20:36     ` Drew Adams
2008-08-02 21:07       ` Jason Rumney
2008-08-02 22:08         ` Drew Adams
2008-08-27 16:41           ` Drew Adams [this message]
2008-08-28 15:04             ` Drew Adams
2008-08-30 14:38               ` Drew Adams
2008-10-31 21:05                 ` Drew Adams
  -- strict thread matches above, loose matches on Subject: below --
2008-12-28  1:32 Chong Yidong
2008-12-28  8:02 ` Drew Adams
2008-12-28  9:00   ` Chong Yidong
2008-12-28 18:15     ` Drew Adams
2008-12-28 19:22 grischka
2008-12-28 19:27 ` Drew Adams

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='000c01c90863$b952b6c0$c2b22382@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=117@emacsbugs.donarmstrong.com \
    --cc=jasonr@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).