From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 60886@debbugs.gnu.org, juri@linkov.net
Subject: bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point
Date: Thu, 19 Jan 2023 11:43:09 +0100 [thread overview]
Message-ID: <9703eeaf-42bf-aeb1-c03b-c3c8700aab48@gmx.at> (raw)
In-Reply-To: <83pmbazvnn.fsf@gnu.org>
> I guess I don't understand the use case then? how can that happen?
With emacs -Q do
M-: (pop-to-buffer "*Messages*")
C-x w 3
> And what would you suggest to say in the doc string instead?
Either nothing or what 'split-window' says in that case: That the new
window shows the buffer of the window selected on the frame containing
the window that was split.
Functions like 'split-window-below' were historically intended for
interactive use only. The Elisp manual said about them
For interactive use, Emacs provides two commands which always split
the selected window.
which apparently is no longer true.
martin
next prev parent reply other threads:[~2023-01-19 10:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 17:10 bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point Juri Linkov
2023-01-18 13:08 ` Eli Zaretskii
2023-01-18 17:13 ` martin rudalics
2023-01-18 17:32 ` martin rudalics
2023-01-18 18:25 ` Juri Linkov
2023-01-18 23:03 ` martin rudalics
2023-01-19 6:34 ` Eli Zaretskii
2023-01-19 8:49 ` martin rudalics
2023-01-19 10:05 ` Eli Zaretskii
2023-01-19 10:43 ` martin rudalics [this message]
2023-01-19 11:32 ` Eli Zaretskii
2023-01-20 9:17 ` martin rudalics
2023-01-21 8:16 ` Eli Zaretskii
2023-01-21 10:08 ` martin rudalics
2023-01-21 11:39 ` Eli Zaretskii
2023-01-21 15:30 ` martin rudalics
2023-01-21 15:55 ` Eli Zaretskii
2023-01-22 9:53 ` martin rudalics
2023-01-26 8:01 ` Eli Zaretskii
2023-01-26 15:44 ` martin rudalics
2023-01-26 16:40 ` Eli Zaretskii
2023-01-21 17:57 ` Juri Linkov
2023-01-22 9:53 ` martin rudalics
2023-01-22 17:09 ` Juri Linkov
2023-01-24 17:55 ` 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=9703eeaf-42bf-aeb1-c03b-c3c8700aab48@gmx.at \
--to=rudalics@gmx.at \
--cc=60886@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
/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).