unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Sean Devlin <spd@toadstyle.org>, 58933@debbugs.gnu.org
Subject: bug#58933: 28.2; project-buffers should take an optional filter
Date: Fri, 04 Nov 2022 06:47:11 +0000	[thread overview]
Message-ID: <87fsezusgg.fsf@posteo.net> (raw)
In-Reply-To: <45027bdd-37ec-5a9e-0cb9-79f6d5df23fa@yandex.ru> (Dmitry Gutov's message of "Fri, 4 Nov 2022 03:22:09 +0200")

Dmitry Gutov <dgutov@yandex.ru> writes:

> On 02.11.2022 16:17, Sean Devlin wrote:
>> Hi Dmitry,
>> 
>>> On Nov 1, 2022, at 7:38 PM, Dmitry Gutov<dgutov@yandex.ru>  wrote:
>>>
>>> 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?
>> Thanks for the pointer—I wasn’t aware of these functions. (I’m still on 28.2.)
>> It looks like these do fit the bill. For example, it looks like I
>> could write:
>> (match-buffers condition (project-buffers project))
>> I can’t see these functions in my local installation of compat
>> (056e3cc), but maybe definitions from Emacs 29 haven’t been added
>> yet? In any case, I’m happy to wait a little bit.
>
> Right, I'm not seeing it in there either. Perhaps it'll get there
> after Emacs 29 is released.

Right, Emacs 29 support is under development, but hasn't been completed
yet: https://git.sr.ht/~pkal/compat/tree/emacs-29.1/item/compat-29.el.

> Philip, is that the plan?

The plan is to be ready by the time Emacs 29 is released.  If possible
and I get to it, it might also be released earlier, but at the very
least I'll be waiting for the feature freeze later this month.





  reply	other threads:[~2022-11-04  6:47 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
2022-11-02 14:17   ` Sean Devlin
2022-11-04  1:22     ` Dmitry Gutov
2022-11-04  6:47       ` Philip Kaludercic [this message]
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=87fsezusgg.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=58933@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --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).