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: question about pop-to-buffer Date: Sun, 30 Sep 2012 16:23:38 +0200 Message-ID: <506855EA.4000601@gmx.at> References: <87ipaxnfdy.fsf@gmail.com> <506747EA.3080906@gmx.at> <5068236C.2030400@gmx.at> <878vbrrcwi.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1349015036 32518 80.91.229.3 (30 Sep 2012 14:23:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 30 Sep 2012 14:23:56 +0000 (UTC) Cc: emacs-devel@gnu.org To: Thierry Volpiatto Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Sep 30 16:24:02 2012 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 1TIKR7-0006Iy-GS for ged-emacs-devel@m.gmane.org; Sun, 30 Sep 2012 16:24:01 +0200 Original-Received: from localhost ([::1]:46878 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TIKR1-0004XK-UL for ged-emacs-devel@m.gmane.org; Sun, 30 Sep 2012 10:23:55 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:39929) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TIKQy-0004X3-NF for emacs-devel@gnu.org; Sun, 30 Sep 2012 10:23:53 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TIKQx-00051q-Py for emacs-devel@gnu.org; Sun, 30 Sep 2012 10:23:52 -0400 Original-Received: from mailout-de.gmx.net ([213.165.64.22]:38556) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1TIKQx-00051l-FO for emacs-devel@gnu.org; Sun, 30 Sep 2012 10:23:51 -0400 Original-Received: (qmail invoked by alias); 30 Sep 2012 14:23:49 -0000 Original-Received: from 62-47-62-159.adsl.highway.telekom.at (EHLO [62.47.62.159]) [62.47.62.159] by mail.gmx.net (mp034) with SMTP; 30 Sep 2012 16:23:49 +0200 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX1+JmLVxGNqJmCijGRwLP0AGl3m9mopncQTJ1AYjZh S4mJXHIQBCi06e In-Reply-To: <878vbrrcwi.fsf@gmail.com> X-Y-GMX-Trusted: 0 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 213.165.64.22 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:153754 Archived-At: > Also, I have noticed that window-right/left can also handle vertical > splitting (I.e I was looking for something like window-above/bottom and > I discover that window-right/left do this). > Maybe that can be documented somewhere? No, and I probably should have called them window--right and window--left, but I faintly recall having called them from somewhere outside window.el. These functions are only useful to avoid writing (and window (window-parent window) (window-next-sibling window))) which is needed for technical reasons because usually the minibuffer window is the "sibling" of the frame's root window and the window tree functions should not work on the minibuffer window. Anyone interested finds the rationale in the comment preceding `window-right'. The functions you are interested in are either `window-next-sibling' and `window-prev-sibling' plus `window-combined-p' where the latter is needed to find out whether any such sibling is horizontally or vertically aligned - an information `window-right' and `window-left' won't give you anyway, or `window-in-direction'. If you tell me more precisely how you want to use them, I can provide more information. martin