unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: emacs-devel@gnu.org
Subject: Re: M-x compile and window splitting
Date: Fri, 01 May 2009 11:36:50 +0200	[thread overview]
Message-ID: <87skjpjhal.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <m363gmxto2.fsf@mid.gehheimdienst.de> (Frank Schmitt's message of "Thu, 30 Apr 2009 13:33:33 +0200")

Frank Schmitt <ich@frank-schmitt.net> writes:

Hi Frank,

>>> In Emacs 23, the window is split vertically instead of horizontally
>>
>> No, it's split horizontally instead of vertically in Emacs speach,
>> see `C-h k C-x 3'.
>
> Rather un-intuitive IMO but however.

Well, yes.  I remember it by asking myself how the two windows are
positioned to each other after the split has been done.

>>> - the change doesn't seem to be mentioned in NEWS (at least I couldn't
>>>   find it)
>>
>> ,----[ /usr/share/emacs/23.0.92/etc/NEWS ]
>> | *** New value nil for split-height-threshold inhibits vertical splitting
>> | unless there's no other window.
>> | 
>> | +++
>> | *** New option split-width-threshold controls horizontal splitting.
>> | 
>> | +++
>> | *** A window can be split horizontally even when it's not full-width.
>> | 
>> | +++
>> | *** New option split-window-preferred-function can be set to a function
>> | to override the default splitting mechanism of display-buffer.
>> `----
>
> I don't think those lines are very helpful for users without deeper
> knowledge of this area in Emacs. At least I don't understand a word of
> those lines.

If you don't understand it after reading the docstrings of all those
four vars, I'd say it might qualify as a documentation bug.

> It is not clear what influences the decision whether to split
> horizontally or vertically.

With `split-window-preferred-function' set to nil (the default) it seems
to prefer horizontal over vertical splitting (which is sensible), but
it's not documented in this var's docstring, nor in `display-buffer'.

Bye,
Tassilo
-- 
          "Emacs is not a development tool but a way of life."
                - David Kastrup in alt.religion.emacs -




  reply	other threads:[~2009-05-01  9:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30 10:31 M-x compile and window splitting Frank Schmitt
2009-04-30 11:00 ` Tassilo Horn
2009-04-30 11:33   ` Frank Schmitt
2009-05-01  9:36     ` Tassilo Horn [this message]
2009-05-02  6:59     ` martin rudalics
2009-05-02 10:26       ` Frank Schmitt
2009-05-02 11:51       ` Juri Linkov
2009-05-02 13:09         ` martin rudalics
2009-05-02 13:40       ` Drew Adams
2009-05-02 19:02         ` martin rudalics
2009-05-03 19:58           ` Stefan Monnier
2009-05-04  8:38             ` martin rudalics
2009-04-30 11:45 ` Juri Linkov

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87skjpjhal.fsf@thinkpad.tsdh.de \
    --to=tassilo@member.fsf.org \
    --cc=emacs-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).