Keyword highlighting
Colour errors, warnings and pod states in output — built-in rules are free, custom rules are Pro.
highlightkeywordscolorsregexerrorswarningslog coloringtriggers
Keyword highlighting
Colour words in terminal output as they appear: errors in red, warnings in yellow, Kubernetes pod states, IP addresses, and your own words or patterns. Only the screen changes. Copying and searching see the text exactly as the program wrote it.
Built-in rules (free)
| Rule | Matches, for example |
|---|---|
| Errors | error, failed, fatal |
| Warnings | warn, warning, deprecated |
| Success | ok, success, passed, done, ready |
| IP addresses | 10.0.4.17 |
| Failing | CrashLoopBackOff and other failing pod states |
| In progress | Pending, ContainerCreating, Terminating |
| Healthy | Running, Completed |
Click Edit on a built-in rule to change its colour or style. To match differently, turn the built-in off and add your own rule. Reset built-ins puts them back as they were.
Custom rules (Pro)
- Open Settings → Terminal → Highlighting.
- Click Add rule.
- Enter a pattern and pick Text or Regex, for example
payment-service, orreq-[0-9a-f]{8}as a regex. - Optionally set Match case and Whole word.
- Choose a colour (one of the theme's colours, which follow the terminal theme, or a custom
#RRGGBB) and a style: Text colour or Background.
Where two rules match the same text, the one higher in the list wins, and your rules come first.
Type sample text in the Preview box to try your rules before you rely on them.
Turn it on or off
- Highlight keywords in Settings, or on the terminal's right-click menu, switches all highlighting.
- Also in full-screen apps extends it to
vim,htop,lessand similar. It's off by default, because those programs draw their own colours.
Good to know
- The line you're typing on isn't highlighted until you run it.
- A regex that doesn't compile is marked Invalid and is skipped.
- If your plan ends, your custom rules are kept but not applied. They show a PRO badge, and you can still delete them.