Diagnosing Missing ANSI Colors in less: A Practical Troubleshooting Guide

Problem Statement

Running less on a file or a pipe that contains ANSI escape sequences often results in plain text output. The color information is silently dropped, making logs, diffs, or command output hard to read. This guide helps you identify why the color is missing and how to restore it.

Diagnostic Table

Condition	Likely Cause	Diagnostic Check
Less shows no color at all.	Missing -R or -r flag.	Inspect command line or $LESS variable.
Color missing only when less is used via a pipe.	Upstream command strips color or lesspipe removes escapes.	Run upstream command directly; check LESSOPEN.
Color works in some terminals but not in others.	Terminal emulator reports limited color support or $TERM is restrictive.	Echo $TERM and run tput colors.
Color still missing after adding -R.	Less compiled without raw character support or terminal lacks ANSI handling.	Run less --version and test with a known‑good color stream.

Ordered Checks and Fixes

1. Verify the less invocation

   Check if less is being called with -R or -r. These flags tell less to pass through raw ANSI codes instead of filtering them.

   # Show the exact command line used
   ps -o args= -p $(pgrep -f 'less')
   # Or, if you are running it manually
   less -R file.txt
   

   If the flag is missing, add it explicitly or set the environment variable:

   LESS='-R' less file.txt
   # or permanently
   export LESS='-R'
   

2. Check the LESS environment variable

   Run:

   echo $LESS
   

   Ensure it contains -R or -r. If it does not, add it temporarily for the current session:

   LESS=-R less file.txt
   

3. Inspect upstream commands when using pipes

   Some commands (e.g., git log) automatically strip color when their output is not a terminal. Test the upstream command without piping:

   git log --color=always | head -5
   

   If you see colors, pipe it to less -R and confirm:

   git log --color=always | head -5 | less -R
   

   If colors are absent, the upstream command itself may be suppressing them. Use --color=always or equivalent flags.

4. Examine LESSOPEN and lesspipe

   The less wrapper script lesspipe can preprocess files. It may remove ANSI codes. Check if LESSOPEN is set:

   echo $LESSOPEN
   

   If it points to lesspipe, temporarily unset it:

   unset LESSOPEN
   less -R file.txt
   

5. Verify terminal color capability

   Run:

   echo $TERM
   

   Then check the number of colors supported:

   tput colors
   

   Values below 8 typically mean limited or no color support. If the terminal reports dumb or similar, colors will be disabled. Use a terminal that supports 256 colors (e.g., xterm-256color) and set TERM accordingly.

6. Confirm less supports raw characters

   Run:

   less --version
   

   Look for the raw feature flag. If absent, you may need to install a full less package or recompile with --enable-raw.

7. Test with a controlled color stream

   Use a simple echo command to ensure less -R renders colors:

   echo -e '\e[32mgreen\e[0m' | less -R
   

   If green appears in green, the terminal and less are functioning correctly. If not, revisit the previous steps.

8. Escalation Criteria

   • Colors still missing after applying -R and ensuring TERM supports 256 colors.
   • Upstream commands do not emit color even with --color=always.
   • Terminal reports tput colors < 8 and cannot be changed.
   • The less binary is custom or stripped down and lacks raw support.

   At this point, consider switching to a different pager (e.g., most or bat) or updating your terminal emulator.

Risk & Considerations

• Using -R will display raw escape sequences as visible characters if the input does not contain ANSI codes. This can clutter the output.
• Modifying the global LESS variable can affect scripts that rely on default behavior. Prefer per‑command flags or a wrapper script.
• Some distributions ship a minimal less that lacks raw support. Check less --version and install the full package if necessary.

Practical Verification Checklist

• Run echo -e '\e[31mred\e[0m' | less -R and confirm red appears in red.
• Check echo $LESS contains -R.
• Run tput colors and ensure the value is at least 8.
• Run less --version and confirm raw support is listed.
• Verify upstream command emits color with --color=always when not piped.

Conclusion

Missing ANSI colors in less typically stem from missing -R flags, upstream suppression, or terminal limitations. By following the ordered checks above, you can pinpoint the exact cause and apply the appropriate fix, restoring a colorful and readable output experience.