unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: martin rudalics <rudalics@gmx.at>
Cc: David Hansen <david.hansen@gmx.net>, emacs-devel@gnu.org
Subject: Re: `split-window-preferred-horizontally'
Date: Sat, 07 Jun 2008 14:23:15 -0400	[thread overview]
Message-ID: <jwvzlpx6r6s.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <484A4520.1050201@gmx.at> (martin rudalics's message of "Sat, 07 Jun 2008 10:21:52 +0200")

>> BTW, shouldn't `sensibly' be the default?
> As soon as we have decided on a reasonable standard behavior.

>> Or even the only acceptable setting (besides setting it to
>> a home-cooked function)?
>> I mean the nil value can be simulated with
>> 
>> (setq split-width-threshold most-positive-fixnum)
>> 
>> and the `horizontal' value can be emulated with
>> 
>> (setq split-height-threshold most-positive-fixnum)
>> 
>> If most-positive-fixnum is too inconvenient, we could accept a nil
>> setting for the thresholds to mean the same as most-positive-fixnum.

> Sounds reasonable.  But how do we present the conventional `vertical'
> default value in the customization interface?

I do not understand the question.  `vertical' is nil, so it's (setq
split-width-threshold most-positive-fixnum).  Right?


        Stefan




  reply	other threads:[~2008-06-07 18:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06 19:44 `split-window-preferred-horizontally' David Hansen
2008-06-06 22:01 ` `split-window-preferred-horizontally' martin rudalics
2008-06-06 22:36   ` `split-window-preferred-horizontally' David Hansen
2008-06-07  8:21     ` `split-window-preferred-horizontally' martin rudalics
2008-06-07 20:16       ` `split-window-preferred-horizontally' David Hansen
2008-06-08 13:07         ` `split-window-preferred-horizontally' martin rudalics
2008-06-08 17:49           ` `split-window-preferred-horizontally' David Hansen
2008-06-09 20:54             ` `split-window-preferred-horizontally' David Hansen
2008-06-10  7:54               ` `split-window-preferred-horizontally' martin rudalics
2008-06-10 14:27                 ` `split-window-preferred-horizontally' Stefan Monnier
2008-06-07  1:44   ` `split-window-preferred-horizontally' Stefan Monnier
2008-06-07  2:29     ` `split-window-preferred-horizontally' Juanma Barranquero
2008-06-07  8:21       ` `split-window-preferred-horizontally' martin rudalics
2008-06-07 12:46         ` `split-window-preferred-horizontally' Juanma Barranquero
2008-06-07 14:41           ` `split-window-preferred-horizontally' martin rudalics
2008-06-07  8:21     ` `split-window-preferred-horizontally' martin rudalics
2008-06-07 18:23       ` Stefan Monnier [this message]
2008-06-07 14:36     ` `split-window-preferred-horizontally' martin rudalics
2008-06-07 18:33       ` `split-window-preferred-horizontally' Stefan Monnier

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=jwvzlpx6r6s.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=david.hansen@gmx.net \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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).