From: Dmitry Gutov <dgutov@yandex.ru>
To: Manuel Uberti <manuel.uberti@inventati.org>,
52465@debbugs.gnu.org, "Philip K." <philip@warpmail.net>
Subject: bug#52465: 29.0.50; Expand project-kill-buffer-conditions
Date: Tue, 14 Dec 2021 05:20:58 +0300 [thread overview]
Message-ID: <19e8760b-00c6-7de9-3157-4c9571196c0f@yandex.ru> (raw)
In-Reply-To: <216fd43d-3282-beae-2efc-f8d9923bc1f3@inventati.org>
Hi Manuel,
On 13.12.2021 16:32, Manuel Uberti via Bug reports for GNU Emacs, the
Swiss army knife of text editors wrote:
> Would it make sense to add two more entries
> project-kill-buffer-conditions? I have this in my configuration:
>
> (dolist (entry (list '(derived-mode . comint-mode)
> '(major-mode . change-log-mode)))
> (add-to-list 'project-kill-buffer-conditions entry t))
>
> I often use project-shell in my projects, so I am happy to close it when
> I do 'C-x p k'.
>
> Also, project-kill-buffers already gets rid of the project VC buffers I
> have opened, so I like to kill the related change-log one as well.
>
> What do you think?
Adding comint-mode sounds fine to me.
Regarding change-log-mode, do you usually have those buffers not saved
to a file? Because otherwise the condition with 'buffer-file-name'
should be used.
next prev parent reply other threads:[~2021-12-14 2:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 13:32 bug#52465: 29.0.50; Expand project-kill-buffer-conditions Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-14 2:20 ` Dmitry Gutov [this message]
2021-12-14 6:28 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-14 16:14 ` Dmitry Gutov
2021-12-14 19:14 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-14 19:42 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-14 23:59 ` Dmitry Gutov
2021-12-15 6:18 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=19e8760b-00c6-7de9-3157-4c9571196c0f@yandex.ru \
--to=dgutov@yandex.ru \
--cc=52465@debbugs.gnu.org \
--cc=manuel.uberti@inventati.org \
--cc=philip@warpmail.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 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.