From: martin rudalics <rudalics@gmx.at>
To: Alex <agrambot@gmail.com>
Cc: 27999@debbugs.gnu.org
Subject: bug#27999: 26.0.50; delete-other-windows deletes side windows
Date: Wed, 09 Aug 2017 12:02:42 +0200 [thread overview]
Message-ID: <598ADDC2.8010903@gmx.at> (raw)
In-Reply-To: <87d187m60t.fsf@lylat>
> I figure that for side windows, it would be more common to want the
> previous behaviour than not. Since if someone wanted to remove all side
> windows, one could use 'window-toggle-side-windows' instead, right?
Right. But IIUC some people wanted side windows for the single purpose
to display a buffer on a chosen side of the frame. Once created, they
want the window to behave like any other ordinary window. They don't
get that because a side window cannot be made the single window of its
frame, cannot be split and the like. Still ...
> In any case, it would be nice to have a better interface for enabling
> (or disabling) this behaviour, rather than using 'set-window-parameter'.
>
> I'd like to suggest an additional (preferably terse) special symbol for
> the alist argument of 'display-buffer-in-side-window' that would inhibit
> window deletion either by delete-other-windows, delete-window, or both.
Then we should probably care about the ‘no-other-window’ parameter as
well. BTW, a ‘no-delete-window’ parameter doesn't exist yet - we would
have to add it first. Currently, you have to set the ‘delete-window’
parameter of the window to 'ignore. Also note that in general it's
easier to just add a parameter than to first have one added and remove
it afterwards.
There is an example in the Elisp manual section 28.19.3 Frame Layouts
with Side Windows. Could you read it first, tell me what is not clear
or clumsy to use. Then we could possibly come up with a better
solution.
> The procedure mentions "a ‘window-parameter’ entry in ALIST", but it
> doesn't mention the form it should be in.
The doc-string of ‘display-buffer’ describes it as
‘window-parameters’ -- Value specifies an alist of window
parameters to give the chosen window.
> I tried a few obvious forms,
> but none were applied. In any case, I believe it's still too
> inconvenient to list out the relevant parameters explicitly in this way.
This should be improved since window parameters should be easily
specifiable in a ‘display-buffer’ alist not only for side windows.
Please make a suggestion.
> P.S. I believe the ‘no-delete-other-window’ parameter should instead be
> ‘no-delete-other-windows’, to match the plurality of
> ‘delete-other-windows’. I made that mistake when first trying to set the
> parameter.
Suppose we added a ‘no-delete-window’ parameter: Its semantics would
probably be to not delete this window. Then a ‘no-delete-other-windows’
parameter's semantics would be to not delete any other windows when
invoked with this window selected. That's why I chose the term without
the "s". Arguably, this reasoning is broken by the ‘no-other-window’
parameter ...
martin
next prev parent reply other threads:[~2017-08-09 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 5:02 bug#27999: 26.0.50; delete-other-windows deletes side windows Alex
2017-08-07 7:56 ` martin rudalics
2017-08-07 21:17 ` Alex
2017-08-09 10:02 ` martin rudalics [this message]
2017-08-18 20:17 ` Alex
2017-08-19 9:11 ` martin rudalics
2017-08-19 9:26 ` martin rudalics
2022-01-23 15:57 ` Lars Ingebrigtsen
2022-02-20 19:31 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=598ADDC2.8010903@gmx.at \
--to=rudalics@gmx.at \
--cc=27999@debbugs.gnu.org \
--cc=agrambot@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.