From: martin rudalics <rudalics@gmx.at>
To: vmontressor@yahoo.com
Cc: help-gnu-emacs@gnu.org
Subject: Want old "*compilation*" behavior back!
Date: Sun, 15 May 2011 09:26:38 +0200 [thread overview]
Message-ID: <4DCF802E.2010704@gmx.at> (raw)
> 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
next reply other threads:[~2011-05-15 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-15 7:26 martin rudalics [this message]
2011-05-17 1:23 ` Want old "*compilation*" behavior back! Vincent Montressor
-- strict thread matches above, loose matches on Subject: below --
2011-05-17 15:17 martin rudalics
2011-05-17 19:50 ` Vincent Montressor
2011-05-13 23:58 Vincent Montressor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DCF802E.2010704@gmx.at \
--to=rudalics@gmx.at \
--cc=help-gnu-emacs@gnu.org \
--cc=vmontressor@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.