From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Window configurations Date: Wed, 02 Jun 2010 10:08:04 -0400 Message-ID: References: <4BB4CF6B.2000007@alice.it> <871vdu6qn5.fsf@mail.jurta.org> <87bpcv1wvt.fsf@mail.jurta.org> <4BE13828.2030609@gmx.at> <87vdb2qo82.fsf@mail.jurta.org> <4BE27C17.3030005@gmx.at> <87vdav4vx5.fsf@mail.jurta.org> <4BE900E7.3090402@gmx.at> <87r5liqv8f.fsf@mail.jurta.org> <4BEA74DC.2060103@gmx.at> <87y6fns8qo.fsf@mail.jurta.org> <4BECF4D6.9030707@gmx.at> <87632na2af.fsf@mail.jurta.org> <4C03F1B5.8040708@gmx.at> <4C04D1BF.9070902@gmx.at> <4C052F8C.8030208@gmx.at> <4C0655BE.2060203@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1275487778 18621 80.91.229.12 (2 Jun 2010 14:09:38 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 2 Jun 2010 14:09:38 +0000 (UTC) Cc: Juri Linkov , Emacs To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 02 16:09:37 2010 connect(): No such file or directory Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OJodQ-0002Uw-JV for ged-emacs-devel@m.gmane.org; Wed, 02 Jun 2010 16:09:32 +0200 Original-Received: from localhost ([127.0.0.1]:56773 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OJodP-0004WO-Vj for ged-emacs-devel@m.gmane.org; Wed, 02 Jun 2010 10:09:32 -0400 Original-Received: from [140.186.70.92] (port=49125 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OJoc6-0003Cl-6K for emacs-devel@gnu.org; Wed, 02 Jun 2010 10:08:11 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OJoc1-0000TH-Ar for emacs-devel@gnu.org; Wed, 02 Jun 2010 10:08:09 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:54488 helo=ironport2-out.pppoe.ca) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OJoc1-0000TC-8q for emacs-devel@gnu.org; Wed, 02 Jun 2010 10:08:05 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEACYCBkxMCpdY/2dsb2JhbACeGnLBG4UWBIxU X-IronPort-AV: E=Sophos;i="4.53,347,1272859200"; d="scan'208";a="67028860" Original-Received: from 76-10-151-88.dsl.teksavvy.com (HELO pastel.home) ([76.10.151.88]) by ironport2-out.pppoe.ca with ESMTP; 02 Jun 2010 10:08:04 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 65E8B81F8; Wed, 2 Jun 2010 10:08:04 -0400 (EDT) In-Reply-To: <4C0655BE.2060203@gmx.at> (martin rudalics's message of "Wed, 02 Jun 2010 14:59:42 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:125455 Archived-At: >> then yes, we probably all agree. > Tracing `with-output-to-temp-buffer' is a pain. I suppose > temp_output_buffer_show needs some reserved value for the second > argument of `display-buffer' so the latter can set up the window-local > buffer list appropriately. I don't want to link with-output-to-temp-buffer and display-buffer. I.e. if it requires something special from display-buffer, then that extra flexibility will have to be added to display-buffer, but not in a "reserved value" kind of way. >> E.g. "immediately" after split-window, any set-window-buffer will not >> push the current buffer on the buffer-list of that window. > Aren't there too many ways to make this `set-window-buffer' happen? Maybe. I think we won't know before we try it. >> > We could make this customizable. > Not really. I want to avoid that changing the established behavior > causes people who do not care anyway ask for getting the old behavior > back. If we make this customizable we can concentrate on the criticism > of people who really do care. I'd rather deal with the disgruntled than add a customization variable. Stefan