From: Juri Linkov <juri@linkov.net>
To: 53870@debbugs.gnu.org
Subject: bug#53870: calendar-exit doesn't kill calendar buffers
Date: Tue, 08 Feb 2022 09:39:24 +0200 [thread overview]
Message-ID: <86tud9erir.fsf_-_@mail.linkov.net> (raw)
In-Reply-To: <87fsotvqff.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 08 Feb 2022 07:11:00 +0100")
[This is a separate bug report from bug#53764.]
>> The only case when I see the diary file is when quitting Calendar
>> leaves the diary buffer floating in the buffer list, so every time after
>> using Calendar have to visit the diary buffer and manually kill it.
>
> That buffer is included in `calendar-buffer-list', so `calendar-exit'
> calls `quit-window' on that buffer. So you could have
> `quit-window-hook' kill the buffer, I guess?
The problem is that when the KILL arg of calendar-exit is non-nil,
it still doesn't kill calendar buffers.
When calendar-setup is non-nil, it doesn't kill all calendar buffers
because ‘(quit-window kill w)’ is called only on windows, but not on
non-displayed buffers.
When calendar-setup is nil, it doesn't kill all calendar buffers
because ‘(quit-windows-on b kill)’ never kills non-displayed buffers.
next prev parent reply other threads:[~2022-02-08 7:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 22:12 bug#53764: 27.1; shouldn't ~/diary be in diary-mode? Francesco Potortì
2022-02-05 6:54 ` Lars Ingebrigtsen
2022-02-05 15:02 ` Francesco Potortì
2022-02-05 21:54 ` Lars Ingebrigtsen
2022-02-05 23:11 ` Francesco Potortì
2022-02-06 23:07 ` Lars Ingebrigtsen
2022-02-07 0:39 ` Michael Heerdegen
2022-02-07 3:45 ` Lars Ingebrigtsen
2022-02-07 4:17 ` Michael Heerdegen
2022-02-07 8:25 ` Lars Ingebrigtsen
2022-02-07 23:50 ` Michael Heerdegen
2022-02-09 18:03 ` Francesco Potortì
2022-02-07 19:39 ` Juri Linkov
2022-02-08 6:11 ` Lars Ingebrigtsen
2022-02-08 7:39 ` Juri Linkov [this message]
2022-02-09 8:32 ` bug#53870: calendar-exit doesn't kill calendar buffers Lars Ingebrigtsen
2022-02-08 1:16 ` bug#53764: 27.1; shouldn't ~/diary be in diary-mode? Phil Sainty
2022-02-07 9:10 ` Francesco Potortì
2022-02-07 9:28 ` Lars Ingebrigtsen
2022-02-09 18:21 ` Francesco Potortì
2022-02-09 21:26 ` Andreas Schwab
2022-02-09 21:52 ` Francesco Potortì
2022-02-06 3:54 ` Michael Heerdegen
2022-02-07 5:08 ` Richard Stallman
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=86tud9erir.fsf_-_@mail.linkov.net \
--to=juri@linkov.net \
--cc=53870@debbugs.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).