From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Lennart Borgman (gmail)" Newsgroups: gmane.emacs.help Subject: Re: MY window tree! Date: Tue, 16 Jan 2007 19:57:31 +0100 Message-ID: <45AD201B.9060009@gmail.com> References: <45A8B034.8020301@gmx.at> <45AA17CE.9050009@gmail.com> <45AA6B59.30203@gmx.at> <45AAA21C.6090505@gmail.com> <45AAB98F.8060404@gmail.com> <45AB2CDB.1040207@gmx.at> <45AB7C99.6050002@gmail.com> <45AB8B1F.7010408@gmail.com> <45AB92A8.7030300@gmail.com> <45ABB942.9070407@gmx.at> <45ABC474.3010208@gmail.com> <45ABD474.9040206@gmx.at> <45ABE387.9010306@gmail.com> <45AC03E2.5080109@gmx.at> <45AC18F4.4@gmail.com> <45AC82D1.1050609@gmx.at> <45ACA9C6.40400@gmail.com> <45ACDFEE.8020608@gmx.at> <45AD1298.2050008@gmail.com> <45AD1A40.1040403@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1168973878 26874 80.91.229.12 (16 Jan 2007 18:57:58 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 16 Jan 2007 18:57:58 +0000 (UTC) Cc: help-gnu-emacs@gnu.org, michael@cadilhac.name Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Jan 16 19:57:56 2007 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1H6tVI-0001EG-Fk for geh-help-gnu-emacs@m.gmane.org; Tue, 16 Jan 2007 19:57:52 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H6tVI-0005YB-5v for geh-help-gnu-emacs@m.gmane.org; Tue, 16 Jan 2007 13:57:52 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H6tV3-0005Xo-N6 for help-gnu-emacs@gnu.org; Tue, 16 Jan 2007 13:57:37 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H6tV0-0005XE-5e for help-gnu-emacs@gnu.org; Tue, 16 Jan 2007 13:57:37 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H6tV0-0005XB-0V for help-gnu-emacs@gnu.org; Tue, 16 Jan 2007 13:57:34 -0500 Original-Received: from [80.76.149.213] (helo=ch-smtp02.sth.basefarm.net) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1H6tUz-0002n2-CM for help-gnu-emacs@gnu.org; Tue, 16 Jan 2007 13:57:33 -0500 Original-Received: from c83-254-145-24.bredband.comhem.se ([83.254.145.24]:61711 helo=[127.0.0.1]) by ch-smtp02.sth.basefarm.net with esmtp (Exim 4.63) (envelope-from ) id 1H6tUw-00083Q-9O; Tue, 16 Jan 2007 19:57:31 +0100 User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) Original-To: martin rudalics In-Reply-To: <45AD1A40.1040403@gmx.at> X-Antivirus: avast! (VPS 0703-2, 2007-01-16), Outbound message X-Antivirus-Status: Clean X-Scan-Result: No virus found in message 1H6tUw-00083Q-9O. X-Scan-Signature: ch-smtp02.sth.basefarm.net 1H6tUw-00083Q-9O dc4995892fa9347df7b107388d3567cd X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:40373 Archived-At: martin rudalics wrote: > >> In any case > >> there's no need to scan the entire `buffer-list' for overlays. Any > >> buffer involved must have been displayed by the old window-tree and > must > >> be displayed by the new window-tree. > > > > > > > > I can not see that a buffer that the buffer must have been displayed by > > the old window-tree. The 'window property might just be there to be > > shown later when the buffer is displayed in that special window. > > But where does the "special window" come from? > > Case 1: The special window was created by `winsav-put-window-tree'. In > this case you set the overlay property to the special window. > > Case 2: The special window was not created by `winsav-put-window-tree'. > In this case the special window must have existed before calling > `winsav-put-window-tree' and there's no need to change the value of the > property. If the property references the window it can be displayed. > Otherwise it was not displayed before and will not be afterwards. > > A window property is not clairvoyant. It may reasonably reference only > a window that exists at the time you assign the property. How does this relate to if the buffer was DISPLAYED in the window tree (ie if window-buffer had that value for any window in the window tree) at the moment winsav-get-window-tree was called?