Question 1

What's the difference between zsh-command-time and Zsh's REPORTTIME?

Accepted Answer

zsh-command-time tracks total elapsed time including idle periods, while REPORTTIME only measures CPU time. This makes zsh-command-time better for commands like sleep or I/O-bound tasks that don't consume much CPU, as explained in the README.

Question 2

How do I exclude commands from being timed?

Accepted Answer

Set the ZSH_COMMAND_TIME_EXCLUDE array in your .zshrc with command names, e.g., ZSH_COMMAND_TIME_EXCLUDE=(vim mcedit). This prevents timing output for those commands, as shown in the configuration section.

Question 3

Can I use zsh-command-time with oh-my-zsh?

Accepted Answer

Yes, download the plugin to ~/.oh-my-zsh/custom/plugins/command-time and add 'command-time' to the plugins list in .zshrc. The README provides step-by-step instructions for oh-my-zsh integration.

Question 4

How to change the colors in the output?

Accepted Answer

Set ZSH_COMMAND_TIME_COLOR to a color name, or use ZSH_COMMAND_TIME_NO_COLOR='1' to disable colorization. The default uses green, yellow, and red based on duration, with details in the configuration examples.

Question 5

Is zsh-command-time compatible with powerlevel9k?

Accepted Answer

The README recommends against it as powerlevel9k has a native segment. If you must use it, you can define a custom element, but this adds complexity and might cause redundant displays, requiring manual setup.

Question 6

How can I customize the time display format?

Accepted Answer

Override the zsh_command_time function in your .zshrc. The README includes an example that formats time into hours, minutes, and seconds with custom colors, allowing full control over the output.

command-time

What is command-time?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions