[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#60886: 29.0.60; split-root-window-below broken for split-window-keep
From: |
Eli Zaretskii |
Subject: |
bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point |
Date: |
Thu, 19 Jan 2023 13:32:25 +0200 |
> Date: Thu, 19 Jan 2023 11:43:09 +0100
> Cc: juri@linkov.net, 60886@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
>
> > 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
This shows *Messages* in the new window, so I think something like
...the same buffer as the window which was selected when the
function was invoked"
should be good.
> > 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.
See above.
> 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.
That doesn't say "only for interactive use", and it would make no
sense to say that for such a basic function, IMO.
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, Juri Linkov, 2023/01/17
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, Eli Zaretskii, 2023/01/18
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, martin rudalics, 2023/01/18
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, martin rudalics, 2023/01/18
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, Juri Linkov, 2023/01/18
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, martin rudalics, 2023/01/18
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, Eli Zaretskii, 2023/01/19
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, martin rudalics, 2023/01/19
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, Eli Zaretskii, 2023/01/19
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, martin rudalics, 2023/01/19
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point,
Eli Zaretskii <=
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, martin rudalics, 2023/01/20
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, Eli Zaretskii, 2023/01/21
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, martin rudalics, 2023/01/21
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, Eli Zaretskii, 2023/01/21
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, martin rudalics, 2023/01/21
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, Eli Zaretskii, 2023/01/21
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, martin rudalics, 2023/01/22
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, Eli Zaretskii, 2023/01/26
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, martin rudalics, 2023/01/26
- bug#60886: 29.0.60; split-root-window-below broken for split-window-keep-point, Eli Zaretskii, 2023/01/26