From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: Redisplay problems? Date: Fri, 21 Mar 2014 09:03:39 +0100 Message-ID: <532BF25B.2070004@gmx.at> References: <87ppljg4ti.fsf@kanru-mozilla.corp.tpe1.mozilla.com> <5329C53B.3030008@gmx.at> <532ABA60.7000003@gmx.at> <532B3FFE.5020403@gmx.at> <83eh1w7gkd.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1395389054 29233 80.91.229.3 (21 Mar 2014 08:04:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 21 Mar 2014 08:04:14 +0000 (UTC) Cc: emacs-devel@gnu.org, christian@defun.dk, monnier@iro.umontreal.ca, kanru@kanru.info, cloos@jhcloos.com To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 21 09:04:23 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WQuRB-0003J4-LO for ged-emacs-devel@m.gmane.org; Fri, 21 Mar 2014 09:04:21 +0100 Original-Received: from localhost ([::1]:51176 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQuR8-0007M8-2S for ged-emacs-devel@m.gmane.org; Fri, 21 Mar 2014 04:04:18 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49469) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQuQu-00077N-2m for emacs-devel@gnu.org; Fri, 21 Mar 2014 04:04:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WQuQm-0003qT-KF for emacs-devel@gnu.org; Fri, 21 Mar 2014 04:04:04 -0400 Original-Received: from mout.gmx.net ([212.227.17.20]:64282) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQuQm-0003qC-AZ; Fri, 21 Mar 2014 04:03:56 -0400 Original-Received: from [62.47.250.12] ([62.47.250.12]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0Lugbo-1X8fLU2LEu-00zpPu; Fri, 21 Mar 2014 09:03:52 +0100 In-Reply-To: <83eh1w7gkd.fsf@gnu.org> X-Provags-ID: V03:K0:ysWl5Soh6RuvHyLNlDdb+EvIWJHwSTgy7k9eED1tg5cPD2pr/sz t2rL0jIv86sFwWeaErAsu3+8pb/uZENLeUw82GYxQpbe9CK9p6qehdffbNVep6A827wtMTd 0DZDmVHCfe7864WXOkYvGtS1uFPOMkLYKyqbUKc8OsbkcEDr3K/qFGUXufiCtcCjCB/Pety 6mrftWBFtk4zZtNfXjZBw== X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 212.227.17.20 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:170689 Archived-At: >> But it's a redraw when we expose a hitherto invisible/obscured frame >> whose contents have changed while it was invisible/obscured. > > If the glyph matrices of such a frame were updated when the contents > changed, then there's no need to recompute them at expose event time. But wasn't the whole idea of maintaining an "obscured" state to not update the glyph matrices when a change occurs while the frame is obscured but instead to wait until the frame gets exposed again? martin