From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: pop-to-buffer / switch-to-buffer-other-window
Date: Sun, 7 Jun 2020 15:55:12 +0900 [thread overview]
Message-ID: <4BD7D31A-E321-433A-B561-20AB3953EAB2@traduction-libre.org> (raw)
In-Reply-To: <91CED84B-6628-4458-92E0-9A6AD7BCC9DF@gnu.org>
> On Jun 7, 2020, at 15:18, Eli Zaretskii <eliz@gnu.org> wrote:
>
> On June 7, 2020 5:55:52 AM GMT+03:00, Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org> wrote:
>> When I have just one window open, switch-to-buffer-other-window
>> sometimes splits vertically and sometimes horizontally to display the
>> other window.
>>
>> In the documentation, there are plenty of references to "some window"
>> but little if anything about how that window is chosen/created.
>>
>> What is the rationale behind this lack of consistency ? Or is there
>> some consistency, for ex based on the mode ?
>
> Please see "Splitting Windows" in the ELisp manual, it describes how Emacs decides whether to split vertically or horizontally.
Do you mean this:
split-window &optional window size *side* pixelwise
It just says that the side argument affects the function, not what in pop-to-buffer causes that argument to be set. And I don't find any reference to splitting in pop-to-buffer for that matter.
--
Jean-Christophe Helary @brandelune
http://mac4translators.blogspot.com
next prev parent reply other threads:[~2020-06-07 6:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 2:55 pop-to-buffer / switch-to-buffer-other-window Jean-Christophe Helary
2020-06-07 6:18 ` Eli Zaretskii
2020-06-07 6:55 ` Jean-Christophe Helary [this message]
2020-06-07 9:57 ` Eli Zaretskii
2020-06-07 11:20 ` Jean-Christophe Helary
2020-06-07 14:33 ` Eli Zaretskii
2020-06-07 15:07 ` Jean-Christophe Helary
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=4BD7D31A-E321-433A-B561-20AB3953EAB2@traduction-libre.org \
--to=jean.christophe.helary@traduction-libre.org \
--cc=eliz@gnu.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).