unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Sean Devlin <spd@toadstyle.org>, 58933@debbugs.gnu.org
Subject: bug#58933: 28.2; project-buffers should take an optional filter
Date: Wed, 2 Nov 2022 01:38:42 +0200	[thread overview]
Message-ID: <0540bf68-7419-f679-ef1c-fb4d8e978a4b@yandex.ru> (raw)
In-Reply-To: <0EDC4306-3724-468F-8F0D-0470304A538D@toadstyle.org>

Hi Sean,

On 01.11.2022 00:04, Sean Devlin wrote:

> Project.el provides a function project-buffers that returns a list of
> buffers associated with the given project. The list is unfiltered,
> meaning any program using it will have to do some work to pick out the
> buffers of interest. It would be useful if the function had an optional
> argument to do this work.
> 
> Project.el already has a function project--buffer-check that validates a
> buffer against a list of conditions. Maybe it should be wired into
> project-buffers to do the job of filtering?

There is also 'match-buffers' and 'buffer-match-p' in the core Emacs 
starting with Emacs 29 (should also be available with the 'compat' package).

What do you think about these alternatives?

We could indeed add a new argument, but perhaps it won't made as much of 
a difference, given those options.





  reply	other threads:[~2022-11-01 23:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 22:04 bug#58933: 28.2; project-buffers should take an optional filter Sean Devlin
2022-11-01 23:38 ` Dmitry Gutov [this message]
2022-11-02 14:17   ` Sean Devlin
2022-11-04  1:22     ` Dmitry Gutov
2022-11-04  6:47       ` Philip Kaludercic
2022-11-04 16:40         ` Sean Devlin
2022-11-04 17:07           ` Philip Kaludercic
2022-11-04 17:11             ` Sean Devlin

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=0540bf68-7419-f679-ef1c-fb4d8e978a4b@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=58933@debbugs.gnu.org \
    --cc=spd@toadstyle.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).