From: Federico Tedin via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Ship Mints <shipmints@gmail.com>
Cc: Dmitry Gutov <dmitry@gutov.dev>, Eli Zaretskii <eliz@gnu.org>,
72300@debbugs.gnu.org
Subject: bug#72300: project.el: detect newly created project contained within another
Date: Mon, 05 Aug 2024 21:56:15 +0200 [thread overview]
Message-ID: <87a5hqyc9s.fsf@gmx.de> (raw)
In-Reply-To: <CAN+1HbpB28NpJK3EQzyCzupufP5KjQCCOoRUVuHBFQZQWWyRPQ@mail.gmail.com> (Ship Mints's message of "Mon, 5 Aug 2024 13:18:00 -0400")
Ship Mints <shipmints@gmail.com> writes:
> This appears to be intentional behavior of project's caching implemented via (vc-file-getprop dir 'project-vc) and
> (vc-file-setprop dir 'project-vc project) in project-try-vc. There is no facility, public API or private, to clear the cache en-masse. One could reset the
> cache via clearing the vector vc-file-prop-obarray (setq vc-file-prop-obarray (make-vector 17 0)) in the absence of an API. You can observe what's
> in your vc-file-prop-obarray for yourself before taking this action.
Ah wow, indeed setting that variable to (make-vector 17 0) does solve
the problem. Thanks! Now I wonder if this could/should be exposed to the
user somehow.
next prev parent reply other threads:[~2024-08-05 19:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 19:54 bug#72300: project.el: detect newly created project contained within another Federico Tedin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-04 8:15 ` Eli Zaretskii
2024-08-05 17:18 ` Ship Mints
2024-08-05 19:56 ` Federico Tedin via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-08-13 1:43 ` Dmitry Gutov
2024-08-13 13:31 ` Ship Mints
2024-08-13 14:50 ` Ship Mints
2024-09-30 1:50 ` Dmitry Gutov
2024-09-30 14:31 ` Ship Mints
2024-09-30 23:10 ` Dmitry Gutov
2024-10-01 20:20 ` Ship Mints
2024-10-01 21:45 ` Dmitry Gutov
2024-09-30 1:35 ` 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=87a5hqyc9s.fsf@gmx.de \
--to=bug-gnu-emacs@gnu.org \
--cc=72300@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=eliz@gnu.org \
--cc=federicotedin@gmx.de \
--cc=shipmints@gmail.com \
/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).