First of all, thank you for building clog. It's a very convenient and useful tool for viewing logs.
Problem
When using:
to display the entire log file, the output is printed directly to the terminal without pager support. For large log files, it is difficult to read because the output cannot be conveniently scrolled or navigated.
Suggested Improvement
It would be great if clog -a could support a pager, so users can:
- Scroll through the output interactively.
- See the current position (e.g. top/bottom indicators or similar navigation hints).
- Navigate efficiently in large log files.
Even better, it would be very helpful if the pager also supported features similar to less, such as:
- Keyword searching (
/pattern)
- Filtering or narrowing the displayed logs
- Potentially more advanced filtering options (for example, SQL-like filtering if that fits the project's design)
Why this would help
When working with large log files, interactive navigation and searching are essential. A built-in pager would make clog a more complete log exploration tool, especially when working with large log files.
First of all, thank you for building clog. It's a very convenient and useful tool for viewing logs.
Problem
When using:
to display the entire log file, the output is printed directly to the terminal without pager support. For large log files, it is difficult to read because the output cannot be conveniently scrolled or navigated.
Suggested Improvement
It would be great if
clog -acould support a pager, so users can:Even better, it would be very helpful if the pager also supported features similar to
less, such as:/pattern)Why this would help
When working with large log files, interactive navigation and searching are essential. A built-in pager would make clog a more complete log exploration tool, especially when working with large log files.