unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Alexander Shukaev <haroogan@gmail.com>
To: "Jorge A. Alfaro-Murillo" <jorge.alfaro-murillo@yale.edu>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: First split horizontally, and then vertically
Date: Wed, 12 Aug 2015 18:06:46 +0200	[thread overview]
Message-ID: <CAKu-7Wze7PH=dNR-w=V=Y8dgPXcK8AqeXoHA8uou=BEKJiSsJA@mail.gmail.com> (raw)
In-Reply-To: <8737zoimzx.fsf@yale.edu>

>> which values should I put into
>> (setq-default split-width-threshold  ?)
>> (setq-default split-height-threshold ?)
>> so that Emacs first splits windows horizontally (until the limit) and only
>> then splits them vertically.
>
>
> I also prefer vertical splitting, I have it set up so that no windows are
> split horizontally unless I do it myself:
>
> #+BEGIN_SRC emacs-lisp
>  (setq split-height-threshold nil)
>  (setq split-width-threshold 150)
> #+END_SRC
>
> You can also try setting split-height-threshold to 0, to make a vertical
> split more likely than a horizontal one.

That's the problem.  I've tried this already, and as soon as I have
some integer (0, for example) in `split-height-threshold' the first
split by `split-window-sensibly' is vertical one, i.e.

+-----+
|     |
+-----+
|     |
+-----+

but I want a horizontal split first

+--+--+
|  |  |
|  |  |
|  |  |
+--+--+

maybe even further (if the size of the monitor permits)

+--+--+--+
|  |  |  |
|  |  |  |
|  |  |  |
+--+--+--+

and only then vertical splits should start.

Concerning

(setq split-height-threshold nil)

as you said, this one forbids vertical splits completely which is also
something I don't like.

Kind regards,
Alexander



  reply	other threads:[~2015-08-12 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-11 20:37 First split horizontally, and then vertically Alexander Shukaev
2015-08-12 14:45 ` Jorge A. Alfaro-Murillo
2015-08-12 16:06   ` Alexander Shukaev [this message]
2015-08-12 16:45     ` Jorge A. Alfaro-Murillo
2015-08-12 19:43       ` Alexander Shukaev

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='CAKu-7Wze7PH=dNR-w=V=Y8dgPXcK8AqeXoHA8uou=BEKJiSsJA@mail.gmail.com' \
    --to=haroogan@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=jorge.alfaro-murillo@yale.edu \
    /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.
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).