You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm playing around with multiple versions of the same binary by separating them into different environments during pixi global install, and for extra distinction I would also like to set environment variables that would fire up by default for each binary without having to set them as shell aliases or type them in manually every time.
For example, I have different versions of Neovim installed, and for specific environments I would like to set specific NVIM_APPNAME environment variables to ensure that each version uses its own configuration and data directories.
I've tried to see if setting envs.[env-name].activation.env in the global manifest would work, but it didn't. Using the latest version of Pixi (v0.66.0):
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm playing around with multiple versions of the same binary by separating them into different environments during
pixi global install, and for extra distinction I would also like to set environment variables that would fire up by default for each binary without having to set them as shell aliases or type them in manually every time.For example, I have different versions of Neovim installed, and for specific environments I would like to set specific
NVIM_APPNAMEenvironment variables to ensure that each version uses its own configuration and data directories.I've tried to see if setting
envs.[env-name].activation.envin the global manifest would work, but it didn't. Using the latest version of Pixi (v0.66.0):Beta Was this translation helpful? Give feedback.
All reactions