Open mghah opened 4 years ago
bump - I've had to uninstall as I noticed when platformio is present it uses the normal system path rather than from whatever terminal its called from. Checked in process.env["PATH"] with and without platformio installed, without is as expected, with uses system default $PATH.
OS: Distributor ID: Debian Description: Debian GNU/Linux bullseye/sid Release: testing Codename: bullseye
Atom: Atom : 1.43.0 Electron: 4.2.7 Chrome : 69.0.3497.128 Node : 10.11.0 platformio: 2.10.0
Same problem. System info • MacOS Catalina: 10.15.4 • Atom: 1.45.0
SOLVED
I had the same ( frustrating problem), luckily I think one of the helper packages I had gave a more useful error.
It's down to the Execution Policy - basically default is to not let power shell run more than single line commands ( so not scripts).
In terminal type: Set ExecutionPolicy -Scope CurrentUser
Then when prompted ExecutionPolicy:Unrestricted
Description
i want to use this atom terminal in a virtual environment but it does not work. i create a virtual environment using conda, activate it, launch atom from it, but the terminal from ide-terminal package still belongs to (base). Furthermore, even when i activate virtual environment from IDE-terminal in atom, it is still stock in base environment. i.e., even though it seems like it has switched to the virtual environment, it still points to base environment and fetches python version and installed packages as if its is still in base env.
Steps to reproduce
Expected behavior: terminal in atom should belong to virtual environment as atom is launched from a virtual env
Actual behavior: terminal in atom defaults to base env even though atom was launched from a virtual env. also after manually changing the env in ide-terminal it still used base env setup.
Reproduces how often: 100%
Versions
OS name and version: macOS Sierra 10.12 Platformio-ide-terminal version:2.10
Additional Information