From fa272816ff6bceecf504c37bd0e4bac2857a344c Mon Sep 17 00:00:00 2001 From: Aleksi Aalto Date: Tue, 22 May 2018 15:20:40 +0300 Subject: [PATCH] global status informs about --prune 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". --- templates/locales/en.yml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/templates/locales/en.yml b/templates/locales/en.yml index 71373d4ac..1379ae246 100644 --- a/templates/locales/en.yml +++ b/templates/locales/en.yml @@ -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,