Wolf Vollprecht

I wonder if changing the VSCode CMake extension (for example) would be worth it - for example here: https://github.com/microsoft/vscode-cmake-tools/blob/7b621f45ca9ab4df486f9ea3bcc5439034cea7a9/src/paths.ts#L251 However, if all extensions would be aware of the "pixi"-PATH then...

Would you be interested in contributing a little tutorial page based on one of these recipes from the wild? I think that would be quite nice!

> We would get the same benefit with mamba 2.0. @isuruf unfortunately, no. With pixi / rattler the linking is done in a completely parallelized / pipelined way using async...

Some experiments with `additional_hash` data here: https://github.com/prefix-dev/pixi/pull/3140

That would certainly be useful. We have been switching to our own fork of `diffy`. Currently doing a huge refactor of the entire codebase but once that's finished we could...

Yeah the `SP_DIR` is a bit of a weird one. Currently we try to get all env variables from the _variant_ and not from the resolved environment, so `SP_DIR` is...

It rings a bell but I don't remember exactly what the issue was or is anymore. I would have to take a deeper look. It might indeed be helpful to...

We have the options these days (thanks to @pavelzw). However, for the build package cache I don't see a super compelling reason to do it. Can you elaborate? Is your...

I have some messy left-overs from an earlier try. I have files like: ``` #!/bin/sh export PATH="/Users/wolfv/.pixi/envs/baz/bin:${PATH}" export CONDA_PREFIX="/Users/wolfv/.pixi/envs/baz" "/Users/wolfv/.pixi/envs/baz/bin/pip" "$@" ``` Where the `.pixi/envs/baz` does _not_ exist anymore. I...

When updating multiple envs, I don't know which one is _currently_ updating (just see the name of the last one that was updated)