From: Lars Ingebrigtsen <larsi@gnus.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 52168@debbugs.gnu.org, Matthias Meulien <orontee@gmail.com>,
Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#52168: 29.0.50; Gnus buffers unexpectedly killed by project-kill-buffers
Date: Wed, 01 Dec 2021 05:25:53 +0100 [thread overview]
Message-ID: <87a6hlar3i.fsf@gnus.org> (raw)
In-Reply-To: <87sfvdmq6h.fsf@posteo.de> (Philip Kaludercic's message of "Tue, 30 Nov 2021 18:52:38 +0000")
Philip Kaludercic <philipk@posteo.net> writes:
> To fix issues like this was the intention behind adding
> project-kill-buffer-conditions (that is yet to be generalised). What I
> believe is happening here is that the *Group* buffer is being matched by
> this condition
>
> (and (derived-mode . special-mode)
> (not (major-mode . help-mode)))
>
> because `gnus-group-mode' derives `special-mode' via
> `gnus-mode'. .newsrc-dribble matches both
>
> buffer-file-name
>
> and
>
> (major-mode . fundamental-mode)
>
> at least on my system. Fixing this specific issue should be possible by
> just adjusting project-kill-buffer-conditions, but it is probably
> desirable to think about how this can be avoided in general, without
> loosing the actual intended functionality of project-kill-buffers.
I guess the issue is that it's pretty difficult to get an include-list
here:
;; Most of the temp buffers in the background:
(major-mode . fundamental-mode)
;; non-text buffer such as xref, occur, vc, log, ...
(and (derived-mode . special-mode)
(not (major-mode . help-mode)))
But... I think this is way too dangerous -- I think you really have to
come up with a include-list instead of going after fundamental-mode and
special-mode buffers.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-12-01 4:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 20:54 bug#52168: 29.0.50; Gnus buffers unexpectedly killed by project-kill-buffers Matthias Meulien
2021-11-29 15:27 ` Lars Ingebrigtsen
2021-11-30 13:20 ` Lars Ingebrigtsen
2021-11-30 18:52 ` Philip Kaludercic
2021-12-01 4:25 ` Lars Ingebrigtsen [this message]
2022-11-04 23:01 ` Dmitry Gutov
2022-11-04 22:50 ` Philip Kaludercic
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=87a6hlar3i.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=52168@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=orontee@gmail.com \
--cc=philipk@posteo.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).