Bozhidar Batsov

Hmm. The tracking is done by this function, which is triggered by `find-file-hook`: ```elisp (defun projectile-track-known-projects-find-file-hook () "Function for caching projects with `find-file-hook'." (when (and projectile-track-known-projects-automatically (projectile-project-p)) (projectile-add-known-project (projectile-project-root)))) ```...

Seems like some NPE, but it's hard to tell from where exactly. When I'm playing locally with dummy git projects everything works just fine. I'll add a bit of extra...

That's because of Helm inserting font-locked strings in the bookmarks file for some reason. See https://github.com/bbatsov/helm-projectile/issues/185 and the related fix.

@gnufied The bookmark's file corruption is Helm-specific for sure. I'm not sure if you're referring to this or to the tracking of known projects not working properly for you.

Not sure how easy it'd be to do something like this, as Projectile mostly delegates to built-in Emacs functionality like `fileloop` in the `projectile-replace-*` commands. A better UI work require...

Can you share you Projectile settings here? Are there any other relevant messages from Projectile in the `*Messages*` buffer? How did you add the project? Does opened a file in...

What's the Projectile version bundled with Doom? I have to admit I'm not familiar with the setup there, but I have some memory it was pinning packages it uses to...

Hmm, what's the output from `M-x projectile-project-info`? Evaluating `M-: (projectile-project-files (projectile-acquire-root))` would also be useful. If you can I'd also suggest to update to the latest Projectile, as 2.8 is...

One issue that I see which such a rule is that it's more or less the same as forbidding the use of procs, as the behavior of `return` there is...

Ah, great point! I had forgotten about it.