I have a big repo but I mostly work in a particular directory in it. Is possible to treat that subdirectory as a separate projectile project? I'd like to have a special prefix for this subproject so that I could use all the projectile commands inside it but still be able to use the full repo with the default prefix.
If that's not possible directly would you mind guiding me to the best of in the source code?
Thank you!
@neojski Running into same issue as well, have you figured out how to make it work with sub projects?
Not really.
My current workflow is opening files that I'll need and then navigate using SPC p b. I wish I could use SPC p h but it is unbearably slow when used in big repository.
you can set projectile-project-root in .dir-locals
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution and understanding!
I also have this problem. I have a big repo of notes with notes split to categories, and some of those contain folders that I would like to treat as subprojects. As when I'm working on a particular category of notes I don't want to see other categories. But I don't want to split these notes to different repos.
I'm not aware of a notion of subprojects, but you can have many projectile projects inside of a source control repo. Either drop a .projectile file in the directory root, or use M-x projectile-add-known-project
M-x projectile-add-know-project does not work. Still (projectile-project-root) return parent project path.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution and understanding!
This issues been automatically closed due to lack of activity. Feel free to re-open it if you ever come back to it.
Most helpful comment
M-x projectile-add-know-projectdoes not work. Still(projectile-project-root)return parent project path.