mise
mise copied to clipboard
dev tools, env vars, task runner
When contributing to a project, developers usually go through a two-step process: - Make sure the system dependencies are present. This is something they can do easily with `rtx install`....
I often find myself having to reference environment variables from others, e.g.: ```sh rtx env-vars TEST_RTX1="1" rtx env-vars TEST_RTX2="{{env.TEST_RTX1}}/bin" rtx error parsing config file: ~/.rtx.toml rtx failed to parse template:...
Setting environment variables from commands that are slow affects all prompt executions, e.g. setting: ```sh mise env-vars TEST_MISE="{{exec(command='sleep 1')}}" ``` which translates into: ```toml [env] TEST_MISE = "{{exec(command='sleep 1')}}" ```...
**Describe the bug** It fails with this output: ```text rtx setting up virtualenv at: /home/redbeard/research/.venv rtx failed to get virtualenv: failed to execute command: ~/.local/share/rtx/installs/python/system/bin/python -m venv /home/redbeard/research/.venv ``` **To...
we should have a field to ensure the version of rtx that's executing is new enough: ```toml min_version = "2023.1.1" ```
the global config's [settings] section should be broken out into its own file: `~/.config/rtx/settings.toml`. This way it's clear that settings only go in this location and can't be in just...
tracing
Currently, when using `rtx activate`, rtx will prepend PATH entries to the very front of PATH, e.g.: ``` PATH="~/.local/share/rtx/installs/java/xx/bin:/usr/bin:..." ``` However this might be more aggressive than it should be....