Skip to content

Make the PATH configurable #246

@fpoli

Description

@fpoli

Currently, rustup needs to be in the PATH used by VS Code. This is not flexible enough for some use cases. See the comment here.

For improved flexibility, we could add an optional configuration field specifying the PATH to be used in place of the one available to VS Code. When such field is empty, Prusti Assitant should still use VS Code's PATH as it currently does.
It is necessary to configure the full PATH instead of just rustup's path, because Prusti internally searches for rustup in the PATH that we pass via Prusti Assistant.

Relevant source files:

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions