all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: kent williams <nkwmailinglists@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: compile, next-error, and vertical frame splitting
Date: Tue, 11 May 2010 15:46:27 -0500	[thread overview]
Message-ID: <AANLkTilYft3ef-C5I6Qxmf_JWsNgZSKMiUeGAG76cWtX@mail.gmail.com> (raw)
In-Reply-To: <83mxw6p66l.fsf@gnu.org>

Thanks. Actually it is documented in NEWS, and I'd looked through it,
but I didn't make the connection between the 'split-window-sensibly'
thing and compilation.

At any rate setting split-width-threshold to nil gets the desired
behavior... well, the behavior I was desiring.


On Tue, May 11, 2010 at 2:52 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Tue, 11 May 2010 12:17:17 -0500
>> From: kent williams <nkwmailinglists@gmail.com>
>>
>> Somewhere between Emacs 22 and Emacs 23, a behavior changed:  If you
>> run a compile, and it's the only window (i.e. if you type C-x 1), when
>> I use the next-error (C-x `) command, it splits the window vertically
>> -- i.e. the source file is next to the compilation buffer.  It used to
>> split it horizontally, so that the source file is under the
>> compilation buffer.
>>
>> I want the old behavior back.  The vertically split frame makes the
>> error messages hard to read due to word wrap.
>>
>> Is there some option I can set or do I have to hack into the lisp code?
>
> The new behavior tries to be smart, and decides how to split based on
> the dimensions of the frame.  You can customize this behavior by
> setting split-height-threshold and split-width-threshold.  See the
> documentation of these variables and of split-window-preferred-function.
>
> This is all in NEWS, btw.
>
>



      reply	other threads:[~2010-05-11 20:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-11 17:17 compile, next-error, and vertical frame splitting kent williams
2010-05-11 19:52 ` Eli Zaretskii
2010-05-11 20:46   ` kent williams [this message]

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=AANLkTilYft3ef-C5I6Qxmf_JWsNgZSKMiUeGAG76cWtX@mail.gmail.com \
    --to=nkwmailinglists@gmail.com \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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.