From: Stefan Kangas <stefan@marxist.se>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 42765@debbugs.gnu.org, "Philip K." <philipk@posteo.net>,
"João Távora" <joaotavora@gmail.com>,
"Stefan Monnier" <monnier@iro.umontreal.ca>
Subject: bug#42765: 26.3; project-find-regexp broken in Emacs 26.3
Date: Thu, 1 Oct 2020 05:50:54 -0700 [thread overview]
Message-ID: <CADwFkm=UGd8HwQsym2hdnEZB2pR5gUfL7AadN22vMuo0dhATvw@mail.gmail.com> (raw)
In-Reply-To: <5b413aad-9bf2-5e84-876f-b3c26ef9cf80@yandex.ru> (Dmitry Gutov's message of "Fri, 14 Aug 2020 17:26:37 +0300")
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 08.08.2020 19:42, Philip K. wrote:
>> I managed to fix this by installing a newer Xref version from ELPA, but
>> I think this situation should be handled more gracefully. Is there a
>> reason that project.el doesn't depend on the newer Xref version?
>
> I have pushed a fix for, hopefully. Commit 319463920c.
>
> It inverts the dependencies, making xref only depend on project.el implicitly,
> by requiring Emacs >= 26.3, and making it work with the older API. And making
> project depend on the latest xref.
>
> Hopefully this reversal won't create any problems when upgrading.
So is there anything more to do here, or should this bug be closed?
next prev parent reply other threads:[~2020-10-01 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 16:42 bug#42765: 26.3; project-find-regexp broken in Emacs 26.3 Philip K.
2020-08-10 1:17 ` Dmitry Gutov
2020-08-10 10:46 ` Philip K.
2020-08-10 10:48 ` Dmitry Gutov
2020-08-10 17:58 ` João Távora
2020-08-14 14:26 ` Dmitry Gutov
2020-10-01 12:50 ` Stefan Kangas [this message]
2020-10-01 17:24 ` Dmitry Gutov
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='CADwFkm=UGd8HwQsym2hdnEZB2pR5gUfL7AadN22vMuo0dhATvw@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=42765@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=joaotavora@gmail.com \
--cc=monnier@iro.umontreal.ca \
--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).