NonGNU ELPA: projectile

Projectile is a project interaction library for Emacs.
It provides a powerful set of features operating at the project
level, as well as simple heuristics to identify projects.

See the README and https://docs.projectile.mx for more details.

Changelog

master (unreleased)

New features

• #2182: Add projectile-todos-in-projects and projectile-multi-occur-in-projects, so every sibling command now has a public generic taking any list of projects behind it and a command for a group of your own is a two-line wrapper for all five.
• #2181: Sapling and Bazaar projects can now list their own ignored files, via the new projectile-sapling-ignored-command and projectile-bzr-ignored-command.
• #2180: Every shell backend can now open in another window (s-p x 4 <key>), not just vterm, eat and ghostel: shell, eshell, ielm, term and the backend-dispatching projectile-run gained -other-window commands.
• #2160: Add projectile-find-file-in-sibling-projects (s-p n f) and projectile-search-in-sibling-projects (s-p n s), which work across the family of related projects rather than just the one you're in.
  • Both are built on projectile-find-file-in-projects and projectile-search-in-projects, which take any list of projects, so a command for a group of your own is a two-line wrapper.
  • A group search puts every match in one *projectile-search* buffer, named relative to the directory containing the group, so each one is labelled with the project it came from.
• #2165: A subproject now has its own project type, so the s-p c m lifecycle commands build a monorepo member with the member's own toolchain - a Rust crate or Go module under a JavaScript repository runs cargo test or go test rather than the repository's npm test. New projectile-subproject-type.
  • A member identified by the same manifest as the repository keeps the repository's type: a pnpm or yarn workspace member holds only a package.json and would otherwise fall back to plain npm.
• #2166: Subprojects now come from the workspace's own member list when the repository declares one - pnpm, npm/yarn/bun, Cargo and go.work - instead of from scanning for manifests, so test fixtures and excluded crates stop showing up as subprojects. Babel's repository goes from 205 to its declared 162. New projectile-subproject-functions.
  • Build tools that compute their members rather than declaring them (Gradle, Bazel) keep using the scan, which is why it remains the fallback.
• #2163: Add projectile-switch-to-buffer-in-sibling-projects (s-p n b), projectile-multi-occur-in-sibling-projects (s-p n o) and projectile-todos-in-sibling-projects (s-p n t), so buffers and annotations follow the same family as files and searches.
  • projectile-switch-to-buffer-in-projects joins the two existing generic commands, and projectile-todos now shares one implementation with its group form.

Changes

• #2184: Rename the options that still broke their naming schemes: projectile-ignored-project-patterns to projectile-ignored-project-regexps (it holds regexps, and since 3.4 "patterns" means globs), projectile-track-known-projects-automatically to projectile-auto-track-known-projects, projectile-watch-directory-limit to projectile-watch-max-directories, projectile-dashboard-recent-files to projectile-dashboard-max-recent-files (a count, not a list) and projectile-session-autosave to projectile-session-auto-save. The old names still work as obsolete aliases.
• #2179: projectile-session-auto-save now defaults to t. projectile-session-restore-on-switch reads what autosave writes, so with the save off by default projectile-session-mode restored layouts it had never recorded and did nothing until you saved one by hand. ... ...