Oh, they should be there if you env is setup property. Here’s what it looks like for me.
█ Creating a Virtual Environment for your Project's Packages
To use this project without activating it in the future, make it your default by running your activate command with the `--default` flag.
✔ Project "wilb/Perl-5.34.0-Windows-Utilities" Has Been Activated
• To add a package to your runtime, type "state install <package name>"
• Learn more about how to use the State Tool, type "state learn"
[wilb/Perl-5.34.0-Windows-Utilities] [...]Projects\Temp\Perl-5.34.0-Windows-Utilities>where perl
A couple things to check:
- Make sure Komodo wasn’t already running when you tried starting it from your CMD Window. I MUST boot fresh.
- Check you Preferences (and Project preferences) > Environment and make sure you’re not overriding
PATH with a hard coded
- Try starting Komodo with
ko.exe instead of
komodo.exe. I can’t remember exactly what the distinction is off the top of my head but I believe
ko.exe is the intended terminal command to start Komodo.