One of Projectile’s key features has always been the ability to cache the files in a project, so next time need to do something with them you’d skip the potentially expensive project file indexing step. The feature has always worked reasonably well, but it suffered from a couple of design flaws that I’ve been meaning to address for a while: The cache for all projects is stored in the same file, which means that often you need to load information that you don’t really need. Also - storing all the cache data in the same file means that there’s a higher chance that the cache would get corrupted for one reason or another. When caching is enabled, Projectile loads the data from the cache file when projectile-mode is enabled. That causes two problems: The mode’s init is slower than it could be The cache is not loaded unless you enable projectile-mode I’m happy to report that I finally got to doing something about the problems listed above!1 In a nutshell: Now each project gets its own cache file in the root of the project’s directory (named .projectile-cache.eld by default)2 The cache is read from disk only when you trigger projectile-find-file for the first time This means that Projectile’s loading time is much snappier if you’re a heavy cache user. I plan more improvements in this area - e.g. adding an option to keep the cache only in memory (without writing it to disk), which is probably fine for most people. To make things better I’ve also reorganized how known projects are initialized, so now no IO operations happen during Projectile’s initialization and it’s lightning fast! To illustrate this with a bit of code: ;; projectile-mode init before ;; ;; initialize the projects cache if needed (unless projectile-projects-cache (setq projectile-projects-cache (or (projectile-unserialize projectile-cache-file) (make-hash-table :test 'equal)))) (unless projectile-projects-cache-time (setq projectile-projects-cache-time (make-hash-table :test 'equal))) ;; load the known projects (projectile-load-known-projects) ;; update the list of known projects (projectile--cleanup-known-projects) (when projectile-auto-discover (projectile-discover-projects-in-search-path)) ;; projectile-mode init now ;; ;; nothing IO-related to show here Last week I’ve started to prepare for the release of Projectile 2.9, which will bring a lot of bug fixes and improvements. I know that a lot of people have probably written off Projectile by now, but I still believe that it has a place in the broader Emacs ecosystem (as a community-driven and more feature-rich alternative of project.el) and the best is yet to come! That’s all I have for you today. Keep hacking! P.S. I’d appreciate it if more Projectile users experimented with the current snapshot package, before Projectile 2.9 gets officially released. See https://github.com/bbatsov/projectile/commit/5061bd8dcd9f4d0e874884272f88b10892d15da3. ↩ You’ll probably want to add this file to your .gitignore. ↩

MetaRedux provides tutorials, guides, and resources for learning and mastering Redux, a state management library for JavaScript applications. Developers can learn about Redux principles, patterns, and best practices for managing application state and building scalable and maintainable frontend applications.

Meta Redux

Projectile has introduced significant caching improvements by creating individual cache files for each project, leading to faster loading times. The cache is now read from disk only when needed, and the initialization process has been optimized to avoid IO operations. Version 2.9 will include multiple bug fixes and is poised to offer enhanced functionality.

Projectile Introduces Significant Caching Improvements