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: Mon, 15 Jan 2007 19:52:48 +0100 Message-ID: <45ABCD80.9020403@gmail.com> References: <45A8B034.8020301@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> <45ABAC9E.9020607@gmail.com> <45ABBB05.9090804@gmx.at> <45ABBE37.9090202@gmail.com> <45ABC0AF.2040601@gmx.at> <45ABC4FB.3090003@gmail.com> <45ABCBA6.3090205@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 1168892404 28318 80.91.229.12 (15 Jan 2007 20:20:04 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 15 Jan 2007 20:20:04 +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 Mon Jan 15 21:20:01 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 1H6Wx5-0006Lv-6f for geh-help-gnu-emacs@m.gmane.org; Mon, 15 Jan 2007 19:53:03 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H6Wx5-0005us-3i for geh-help-gnu-emacs@m.gmane.org; Mon, 15 Jan 2007 13:53:03 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H6Wwq-0005uB-1A for help-gnu-emacs@gnu.org; Mon, 15 Jan 2007 13:52:48 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H6Wwo-0005t3-Oj for help-gnu-emacs@gnu.org; Mon, 15 Jan 2007 13:52:47 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H6Wwo-0005sm-HX for help-gnu-emacs@gnu.org; Mon, 15 Jan 2007 13:52:46 -0500 Original-Received: from [80.76.149.212] (helo=ch-smtp01.sth.basefarm.net) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1H6Wwn-00072r-O8 for help-gnu-emacs@gnu.org; Mon, 15 Jan 2007 13:52:46 -0500 Original-Received: from c83-254-145-24.bredband.comhem.se ([83.254.145.24]:62003 helo=[127.0.0.1]) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.63) (envelope-from ) id 1H6Wwl-0000Ii-4g; Mon, 15 Jan 2007 19:52:43 +0100 User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) Original-To: martin rudalics In-Reply-To: <45ABCBA6.3090205@gmx.at> X-Antivirus: avast! (VPS 0703-1, 2007-01-15), Outbound message X-Antivirus-Status: Clean X-Scan-Result: No virus found in message 1H6Wwl-0000Ii-4g. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1H6Wwl-0000Ii-4g d92baac303fea645fd35eeef1f6c7e7a 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:40332 Archived-At: martin rudalics wrote: > >> > I can not see why only displayed buffers should be interesting. A > >> buffer > >> > that is not currently displayed could also have a 'window property > >> > pointing to some of those windows we are interested in. Or? > >> > >> No. A dead window is never resurrected. The window property of that > >> overlay is of no use until you reassign it the value of a live window. > > > > > > > > Maybe we are miscommunicating. I am talking about displayed BUFFERS > > while I wonder if you and Juanma perhaps talks about displayed WINDOWS. > > > > Or am I misunderstanding something? > > Above you said "a buffer ... could have a 'window property". I don't > know of such a property of a buffer. I've been always talking about > overlays with a 'window property. Overlays belong to a buffer. Note > that a buffer can have two or more overlays with different window > properties. Hence the buffer's text may appear differently when it is > simultaneously displayed in two windows. When I remove the 'window > property from an overlay the overlay should appear in all windows > displaying the buffer the overlay belongs to. Sorry, I should have written "A buffer that is not currently displayed IN ANY WINDOW could also have AN OVERLAY WITH a 'window property...". This was supposed to be the answer to your question "Why check all buffers?" - I still do not understand what you mean here. Did you want to write all WINDOWS?