From: Dmitry Gutov <dgutov@yandex.ru>
To: Juri Linkov <juri@linkov.net>
Cc: "Philip K." <philip@warpmail.net>, 41868@debbugs.gnu.org
Subject: bug#41868: [PATCH] Add project-clean-up command
Date: Tue, 16 Jun 2020 03:23:00 +0300 [thread overview]
Message-ID: <c14bc9d2-ee51-b1ba-515f-743ca7bf3ff6@yandex.ru> (raw)
In-Reply-To: <87d060dktc.fsf@mail.linkov.net>
On 16.06.2020 01:49, Juri Linkov wrote:
>>> +(defcustom project-spare-buffers-regexps
>>> + '("\\*Help\\*")
>>
>> Perhaps also call this project-buffer-spare-conditions?
>
> I think the suffix ‘-regexps’ is fine. The problem is that
> the word “spare” has no reference to the related command name
> ‘project-kill-buffers’. Maybe better would be something like
> ‘project-kill-buffers-ignore-regexps’ or
"kill or spare", no? But it's not immediately obvious for non-native
speakers, sure.
>> Or something like that. Point is, no tie the name to regexps, for easy
>> extension into having functions in that list as well.
>
> For functions it's easy to add a separate variable like
> ‘project-kill-buffers-ignore-functions’.
I don't see why we wouldn't want to keep it on the same variable. It's
both easier to document, and to implement.
next prev parent reply other threads:[~2020-06-16 0:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 10:00 bug#41868: [PATCH] Add project-clean-up command Philip K.
2020-06-15 11:04 ` Basil L. Contovounesios
2020-06-15 11:32 ` Philip K.
2020-06-15 11:38 ` Basil L. Contovounesios
2020-06-15 12:28 ` Dmitry Gutov
2020-06-15 18:18 ` Philip K.
2020-06-15 20:50 ` Dmitry Gutov
2020-06-15 21:50 ` Philip K.
2020-06-16 10:19 ` Dmitry Gutov
2020-06-16 10:52 ` Basil L. Contovounesios
2020-06-16 14:31 ` Eli Zaretskii
2020-06-16 17:12 ` Philip K.
2020-06-18 1:05 ` Dmitry Gutov
2020-06-18 6:46 ` Philip K.
2020-06-18 13:04 ` Dmitry Gutov
2020-06-18 14:11 ` Philip K.
2020-06-18 15:36 ` Dmitry Gutov
2020-06-18 22:06 ` Juri Linkov
2020-06-18 22:57 ` Dmitry Gutov
2020-06-18 23:02 ` Juri Linkov
2020-06-18 23:10 ` Dmitry Gutov
2020-06-18 23:18 ` Juri Linkov
2020-06-18 23:29 ` Dmitry Gutov
2020-06-26 0:49 ` Dmitry Gutov
2020-06-19 6:28 ` Philip K.
2020-08-14 17:05 ` Lars Ingebrigtsen
2020-08-14 20:36 ` Dmitry Gutov
2020-06-19 6:20 ` Eli Zaretskii
2020-06-15 22:49 ` Juri Linkov
2020-06-16 0:23 ` Dmitry Gutov [this message]
2020-06-16 21:47 ` Juri Linkov
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=c14bc9d2-ee51-b1ba-515f-743ca7bf3ff6@yandex.ru \
--to=dgutov@yandex.ru \
--cc=41868@debbugs.gnu.org \
--cc=juri@linkov.net \
--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 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).