Follow-up: Switching to project.el

A long while ago (in February this year) I got nice comment from Mike on my switch to project.el

That said, I was surprised to see your comment about having to set vc-handled-backends to nil because otherwise vc interferes with magit, as I have not seen any such conflicts myself, and I made the transition to project.el several years ago.

Maybe it's not worth it to get into it: you obviously found a straightforward workaround, and perhaps there's additional background that you simply didn't include, or I'm over-interpreting "interfere" when you just mean some quirk that I just no longer notice having lived with it for long enough—but it seemed worth it to mention that this may not be universal, and thus might be worth looking into?

I did a search through my commit history and found that I disabled it in August 2024:

Disable VC completely

Apparently VC was activated when loading the config as all of it is in git repos (thanks to straight). This resulted in a question about following a symbolic link in a git repo (thanks to 'vs-follow-links being set to 'ask). I could have turned off the asking, but since I prefer to use magit anyway and I don't use any other VCS I decided to turn VC off completely for now.

Yes, there's a type in there, vs-follow-links should be vc-follow-symlinks I believe.

I reverted about two years later when I switched to elpaca:

Remove the config for VC

It looks like the need for disabling VC disappeared with the move from straight. Now only .projectile is an extra marker for projects.

I would be very surprised if my workaround is still needed when using straight.