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
When working on various remote hosts, it would be nice to prefix the remote COMMAND with something. This could either because the remote is shared, warranting prefixing all command with nice -n 5, or because the command needs to run inside some docker container with docker run, or because it has to queued in some job system such as SLURM.
Specifically, the command here would be nice to if it could be prefixed.
One way this could be configured in .remotes.toml would be:
When working on various remote hosts, it would be nice to prefix the
remote COMMAND
with something. This could either because the remote is shared, warranting prefixing all command withnice -n 5
, or because the command needs to run inside some docker container withdocker run
, or because it has to queued in some job system such as SLURM.Specifically, the command here would be nice to if it could be prefixed.
One way this could be configured in
.remotes.toml
would be:This way enables you to have both a default prefix, with the option to override it per remote host
The text was updated successfully, but these errors were encountered: