sebastiw
the edts-shell could set the code path as the project-node
That seems like a reasonable way of opening a shell to mess with the code without using the project node that edts itself is using for other interactions
How would you choose which project to use as a base? Based on the current module at call-time? It could work but doesn't feel perfect.
Mmmm, yes that is a good point. Maybe you can pass the project as argument and default to the current module?
Yeah, I guess that could work, even though I don't like queries. Perhaps it could be configurable somehow. I wonder what a sane default would be :P
I was thinking on something like changing buffer, that goes to the last one if you don't say anything but you also have the option to choose.
I think that 99.99% of the time you want to go to the shell defined by the project that holds the module you are in, but you already noticed some users have weird tastes :P
If you can branch-off an experiment branch with just the default thing I offer myself to test it
On 27 November 2012 18:31, Thomas Järvstrand [email protected]:
Yeah, I guess that could work, even though I don't like queries. Perhaps it could be configurable somehow. I wonder what a sane default would be :P
— Reply to this email directly or view it on GitHubhttps://github.com/tjarvstrand/edts/issues/29#issuecomment-10767644.
Samuel
