Timeline for project.el: override project root with dir-local var?
Current License: CC BY-SA 4.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 21, 2024 at 7:59 | answer | added | Zenkie Zhu | timeline score: 0 | |
| Sep 29, 2021 at 20:13 | comment | added | Dmitry | All right, and thanks in advance. It's unlikely to be accepted into Emacs 28 in a few weeks (the release window is closing), but we can distribute the updated version through GNU ELPA. | |
| Sep 29, 2021 at 19:50 | comment | added | GaryO | I can't test it right now (will in a few weeks), but it looks like exactly what I was asking for. Thanks!! | |
| Sep 29, 2021 at 11:28 | comment | added | Dmitry | So if you could test the patch, it would be helpful. | |
| Sep 28, 2021 at 21:34 | comment | added | Dmitry | And the second question here in comments was to determine whether the premise for the approach taken in the patch has a good justification. | |
| Sep 28, 2021 at 21:32 | comment | added | Dmitry | I have a patch with a particular approach, and I was wondering whether it will work in your case: debbugs.gnu.org/cgi/bugreport.cgi?bug=41572#85. Sounds like it should work. | |
| Sep 28, 2021 at 21:20 | comment | added | GaryO | To be honest, at the time I wasn't super inclined to dig into the implementation to know why it was wrong. If I remember, my case was a Typescript/Vue app in a larger git monorepo, which might work fine now -- I guess I was hoping for a general "escape hatch" rather than a smarter root autodetection (though that's always great too!) | |
| Sep 28, 2021 at 15:40 | comment | added | Dmitry | I'm asking about particular reasons the project root is detected where it is detected. To be able to choose the optimal technical implementation. | |
| Sep 28, 2021 at 12:13 | comment | added | GaryO | What I meant by "specifically the project is part of a larger project" is that project.el thinks the project is rooted at /a/b/c/d (for whatever reason), but I want to override that so the project root is /a/b, which conceptually is my project root. So in my case there are no subprojects, just one big project to search. | |
| Sep 27, 2021 at 11:44 | comment | added | Dmitry | And if it's the former: would you want to "parent" project to still be able to include subproject's files as its own? And have project-find-file and project-find-regexp always search across subprojects? | |
| Sep 27, 2021 at 11:43 | comment | added | Dmitry | Two questions: do you mean that the project root would be a subdirectory of a large Git (mono)repo? Or that you want the project to be larger than the current Git repo? | |
| Apr 2, 2021 at 17:23 | vote | accept | GaryO | ||
| Apr 2, 2021 at 12:16 | answer | added | Michael | timeline score: 4 | |
| May 12, 2020 at 16:03 | answer | added | Dmitry | timeline score: 4 | |
| May 12, 2020 at 14:26 | history | asked | GaryO | CC BY-SA 4.0 |