From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.help Subject: Want old "*compilation*" behavior back! Date: Sun, 15 May 2011 09:26:38 +0200 Message-ID: <4DCF802E.2010704@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: dough.gmane.org 1305444417 14999 80.91.229.12 (15 May 2011 07:26:57 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 15 May 2011 07:26:57 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: vmontressor@yahoo.com Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun May 15 09:26:54 2011 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QLVj1-0006ff-O0 for geh-help-gnu-emacs@m.gmane.org; Sun, 15 May 2011 09:26:51 +0200 Original-Received: from localhost ([::1]:48658 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QLVj0-0004RO-TX for geh-help-gnu-emacs@m.gmane.org; Sun, 15 May 2011 03:26:50 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:54994) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QLViu-0004RI-T4 for help-gnu-emacs@gnu.org; Sun, 15 May 2011 03:26:45 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QLViu-0003eo-5Q for help-gnu-emacs@gnu.org; Sun, 15 May 2011 03:26:44 -0400 Original-Received: from mailout-de.gmx.net ([213.165.64.22]:47064) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1QLVit-0003eF-P7 for help-gnu-emacs@gnu.org; Sun, 15 May 2011 03:26:44 -0400 Original-Received: (qmail invoked by alias); 15 May 2011 07:26:39 -0000 Original-Received: from 62-47-61-138.adsl.highway.telekom.at (EHLO [62.47.61.138]) [62.47.61.138] by mail.gmx.net (mp004) with SMTP; 15 May 2011 09:26:39 +0200 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX1/PRyNcGk3PI7cJCzgDt6cFzG4RJxNRIggWIUIT+N ifACEvKjk9hUHX User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) Original-References: 447832.87442.qm@web161406.mail.bf1.yahoo.com X-Y-GMX-Trusted: 0 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 213.165.64.22 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:80982 Archived-At: > In Emacs 21, if I split a window > vertically and was in the left-hand buffer ... yet another argument to change the current vertical/horizontal terminology ;-) Please accept for the moment that splitting a window "vertically" produces two windows above each other. To get two windows side-by-side you have to split a window "horizontally". > and did `M-x compile', the > *compilation* buffer would appear in the right-hand buffer (unless the > left-hand > buffer was already *compilation*, in which case it would be reused). In > general, it put *compilation* in the "next" buffer unless there was only one > buffer, in which case it would split the buffer. In the preceding lines you mean "window" instead of "buffer". > In Emacs 23, it reuses the *compilation* buffer if that buffer is already > visible, but otherwise it splits my current buffer instead of using the > existing > "next" buffer. Does it happen with emacs -Q as well? When on my trunk (which is a couple of weeks old) I do emacs -Q, split the *scratch* window into two side-by-side windows and do M-x compile, the right window is reused for the *compilation* buffer. > I liked the old behavior much better, but I don't see a way to get it back. > Any > help? It depends on whether you want a solution just for the compilation buffer or a more general solution. In the latter case, changing the values of `split-height-threshold' or `split-width-threshold' might help. martin