From: martin rudalics <rudalics@gmx.at>
To: pillule <pillule@riseup.net>
Cc: Sujith Manoharan <sujith.wall@gmail.com>, 48493@debbugs.gnu.org
Subject: bug#48493: 28.0.50; quit-window doesn't work
Date: Tue, 25 May 2021 08:50:10 +0200 [thread overview]
Message-ID: <f039b256-4def-2dde-512f-06acbf652744@gmx.at> (raw)
In-Reply-To: <878s434ls1.fsf@host.localdomain>
> Then I suppose that the dedicated window parameter must be restored
> after a kill-buffer accordingly; this solve the previous test but
> ask for more modifications.
Who makes any of these buffers dedicared?
> I can modify to `switch-to-prev-buffer' (and its sibling
> `switch-to-prev-buffer') to return nil instead of the current buffer;
> however the result is the same : the window rest in place with an
> undesired buffer inside.
> Note that we may want that anyway if it can solve the cases where
> `quit-restore-window' display the same buffer again.
>
> I am still looking to find what may be messing the prev-buffers list.
Try to experiment with an idiom like
(if prev-buffer
;; If a previous buffer exists, try to switch to it. If that
;; fails for whatever reason, try to delete the window.
(unless (switch-to-prev-buffer window bury-or-kill)
(window--delete window nil (eq bury-or-kill 'kill)))
;; If no previous buffer exists, try to delete the window. If
;; that fails for whatever reason, try to switch to some other
;; buffer.
(unless (window--delete window nil (eq bury-or-kill 'kill))
(switch-to-prev-buffer window bury-or-kill)))
martin
next prev parent reply other threads:[~2021-05-25 6:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 3:21 bug#48493: 28.0.50; quit-window doesn't work Sujith Manoharan
2021-05-18 8:01 ` martin rudalics
2021-05-18 10:23 ` Sujith Manoharan
2021-05-18 13:31 ` martin rudalics
2021-05-19 7:43 ` martin rudalics
2021-05-24 14:53 ` pillule
2021-05-24 16:51 ` martin rudalics
2021-05-25 1:58 ` pillule
2021-05-25 6:50 ` martin rudalics [this message]
2021-05-25 13:01 ` pillule
2021-05-25 16:28 ` martin rudalics
2021-05-26 16:10 ` pillule
2021-05-27 7:47 ` martin rudalics
2021-06-07 23:23 ` pillule
2021-06-08 9:24 ` pillule
2021-06-09 8:33 ` martin rudalics
2021-06-09 12:34 ` pillule
2021-06-09 13:00 ` pillule
2021-06-09 13:36 ` pillule
2021-06-13 8:49 ` martin rudalics
2021-06-13 9:28 ` pillule
2021-06-13 14:52 ` martin rudalics
2021-06-14 8:28 ` martin rudalics
2021-06-15 16:53 ` pillule
2021-06-08 12:09 ` Eli Zaretskii
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=f039b256-4def-2dde-512f-06acbf652744@gmx.at \
--to=rudalics@gmx.at \
--cc=48493@debbugs.gnu.org \
--cc=pillule@riseup.net \
--cc=sujith.wall@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.