Thank you for your answer! I also found your blog and blogpost: My Julia workflow, and I realised that I have much to learn from you.
One follow-up question: Why do I have to pkg> activate every time I want to run anything from the project? Isn’t all the waltzing with Manifest.toml and Project.toml enough? Or putting it in a different way, what variable does the activate update and how does it enable julia to find my code? I thought the activate was only for Pkg and that code loading relied on the .toml files.
For example, in a newly created directory TestProj:
] activate .
] generate TestMod
] develop --local TestMod
> using TestMod
This works and gives me a false sense of having set up a working environment. But if I exit and re-enter julia:
> using TestMod
ERROR: ArgumentError: Package TestMod not found in current path:
- Run `import Pkg; Pkg.add("TestMod")` to install the TestMod package.
I have to ] activate . again merely for using to work, even if no Pkg managing actions are to take place.
I apologise for the long post, I’m just trying to expose my thinking so that you people can point out the flaws in it.