diff options
Diffstat (limited to 'docs/it-IT/faq')
-rw-r--r-- | docs/it-IT/faq/README.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/it-IT/faq/README.md b/docs/it-IT/faq/README.md index 00589c711..21fbfc7b3 100644 --- a/docs/it-IT/faq/README.md +++ b/docs/it-IT/faq/README.md @@ -69,13 +69,13 @@ Se vedi simboli che non riconosci puoi usare `starship explain` per la spiegazio You can enable the debug logs by using the `STARSHIP_LOG` env var. These logs can be very verbose so it is often useful to use the `module` command if you are trying to debug a particular module, for example, if you are trying to debug the `rust` module you could run the following command to get the trace logs and output from the module. ```sh -env STARHIP_LOG=trace starship module rust +env STARSHIP_LOG=trace starship module rust ``` If starship is being slow you can try using the `timings` command to see if there is a particular module or command that to blame. ```sh -env STARHIP_LOG=trace starship timings +env STARSHIP_LOG=trace starship timings ``` This will output the trace log and a breakdown of all modules that either took more than 1ms to execute or produced some output. @@ -117,6 +117,6 @@ Se Starship è stato installato utilizzando un gestore di pacchetti, fai riferim Se Starship è stato installato utilizzando lo script di installazione, il seguente comando eliminerà il file binario: ```sh -# Individua ed elimina il binario di starship -sh -c 'rm "$(which starship)"' +# Locate and delete the starship binary +sh -c 'rm "$(command -v 'starship')"' ``` |