Using VS code Mojo plugin with pixi virtual environment

Mojo VS Code Extension
1

Hello.
Can anyone explain how to configure VS code plugin for work with pixi virtual environment ?
As far as I understand at the moment, this is the only supported plugin for Mojo (pycharm version do not develop).

I have installed mojo as per the instructions using pixi, since it is a recommended option and only seems to contain all the necessary component. And now I want to use the created pixi virtual environment in VS code. But instead VS code downloads another old copy of mojo witch magic.

The extension description says that i must use MODULAR_HOME witch “/absolute/path/to/. modular”, but there is no . modular folder. I haven’t found any explanation in the documentation or on the internet.

Can anyone describe in detail where and how to specify the correct path?

Path for my project looks like this: /home/user/IdeaProjects/Pycharm/mojo-pixi-project/

If i need additional changes for bash, zsh, fish please let me know too.

I use Arch Linux if it matters.
Thanks.

2

I got the direnv extension to work! I My.envrc file has the following content:

watch_file pixi.lock 
eval "$(pixi shell-hook)"
3

Well, now the console in VS code really allows me to work with a new version of mojo , but when trying to run a file from VS code I get an error message even if I want to run hello world.
VS code still trying to use mojo installed elsewhere. And if VS code can’t find it by the standard route, download it again. Should I do something else?

3
31595×1000 108 KB

trying to install the nightly version of the plugin causes VS code to download another copy of the mojo through magic, which also does not work

4

Currently, the VS Code nightly and stable extensions use an internal copy of Magic to download the Conda packages for the latest nightly and stable release of MAX, respectively. This is unfortunately independent of the version of Mojo / MAX used in your Pixi environment or Python virtual environment. If you’re using the latest nightly / stable release in your environment, you won’t notice much of a difference in what VS Code reports, but these two can diverge if you’re using different pinned versions in your environment.

We’re planning a revamp of the VS Code extension to allow for better interactions with virtual environments and more, but I can’t promise a timeline on that.

5

Okay, I’ll wait for it to happen. I understand correctly that there is currently no IDE, which works properly with Mojo in pixi or uv virtual environment ? For me it is strange that the installation instruction suggests creating a virtual environment, which cannot be used in the IDE.
Can you tell how to change the location where the mojo copy will be downloaded ? I don’t want to keep 1.5 Gb in this path /home/name/. config/Code/User/globalStorage/modular-mojotools.vscode-mojo/magic-data-home/ Or ask VS code don’t download it in principle, so as not to waste space on disk?