Skip to content

Commit

Permalink
global status informs about --prune
Browse files Browse the repository at this point in the history
It's not obvious from the old explanation, how to get
rid of get rid of data that "may not be completely
up-to-date".
  • Loading branch information
Aga303 committed May 22, 2018
1 parent dfb2a9e commit fa27281
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions templates/locales/en.yml
Original file line number Diff line number Diff line change
Expand Up @@ -182,9 +182,10 @@ en:
global_status_footer: |-
The above shows information about all known Vagrant environments
on this machine. This data is cached and may not be completely
up-to-date. To interact with any of the machines, you can go to
that directory and run Vagrant, or you can use the ID directly
with Vagrant commands from any directory. For example:
up-to-date (use "vagrant global-status --prune" to prune invalid
entries). To interact with any of the machines, you can go to that
directory and run Vagrant, or you can use the ID directly with
Vagrant commands from any directory. For example:
"vagrant destroy 1a2b3c4d"
global_status_none: |-
There are no active Vagrant environments on this computer! Or,
Expand Down

0 comments on commit fa27281

Please sign in to comment.