From 4c91c5e02ee00cab7e82fdf6c7b86b9c70c8dad6 Mon Sep 17 00:00:00 2001 From: Dominik Ritter Date: Thu, 16 Feb 2017 21:11:31 +0100 Subject: [PATCH] Add documentation for the `command_execution_time` segment --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 286f7ffe..3c9dff3f 100644 --- a/README.md +++ b/README.md @@ -140,7 +140,7 @@ The segments that are currently available are: **Other:** * [`custom_command`](#custom_command) - Create a custom segment to display the output of an arbitrary command. -* [`command_execution_time`] - Display the time the current command took to execute. +* [`command_execution_time`](#command_execution_time) - Display the time the current command took to execute. * [`todo`](http://todotxt.com/) - Shows the number of tasks in your todo.txt tasks file. * `detect_virt` - Virtualization detection with systemd @@ -205,6 +205,9 @@ without affecting the icon color. Display the time the current command took to execute if the time is above `POWERLEVEL9K_COMMAND_EXECUTION_TIME_THRESHOLD` (defaults to 3 seconds). +The time is shown human readable, if it exceeds one minute. If you want more +precision, just set `POWERLEVEL9K_COMMAND_EXECUTION_TIME_PRECISION=2` (or +whatever precision you want). ##### custom_command