website/docs/proto/commands/setup.mdx
The proto setup command will setup proto in your current shell by modifying an applicable profile
file and appending proto's bin directory to PATH. If a shell could not be detected, you'll be
prompted to select one.
$ proto setup
During setup, the following profiles will be searched or prompted for.
~/.bash_profile~/.bashrc~/.profile~/.elvish/rc.elv~/.config/elvish/rc.elv~/.config/fish/config.fish~/.config/ion/initrc~/.murex_preload~/.murex_profile~/.config/nushell/env.nu~/.config/nushell/config.nu~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1~\Documents\PowerShell\Profile.ps1~/.config/powershell/Microsoft.PowerShell_profile.ps1~/.config/powershell/profile.ps1~/.config/xonsh/rc.xsh~/.xonshrc~/.zprofile~/.zshenv~/.zshrcIn addition to updating a shell profile file (most likely PowerShell), we'll also modify the PATH
(or Path) system environment variable, by prepending the ~/.proto/shims and ~/.proto/bin
paths.
If you would like to opt-out of this behavior, pass the --no-modify-path flag.
--shell - Shell to explicitly setup for.--no-modify-profile / PROTO_NO_MODIFY_PROFILE - Don't update a shell profile file.--no-modify-path / PROTO_NO_MODIFY_PATH - Don't update the system PATH environment variable
(Windows only).--yes - Avoid interactive prompts and use defaults.