New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
using less for live log viewing with columnisation #112
Labels
Comments
calestyo
changed the title
using less for live log parsing with columnisation
using less for live log viewing with columnisation
Jan 6, 2021
You might like |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey.
Not sure what the following is, maybe a question or maybe (1-n) feature requests ;-)
I guess many people use less to view log files or similar output that is continuing.
The problem though seems that while following, none of the usual navigation commands (scrolling up/down, searching or search terms highlighted, right/left when not wrapping words) seems to work.
Would that be feasible?
Especially also, that e.g. new lines don't cause less to jump to the last line, but input is just buffered ... and there is a command which causes it to stick to the last line again?
I think there are actually two ways here:
Think of it like a GUI Terminal, which are always in F mode even if one scrolls up (they still record any output), but when one scrolls up they don't follow the last line anymore, until one presses a key (when they jump down) or scrolls all the way down (when they also stick to the last line again).
So for less I think it would be nice if per default it would stick to the last line, even when moving right/left, but as soon as one goes up it stops (while still recording output). Similarly, it should stop to stick to the line when one presses some command key.
Last but not least, only that same command key should make it sticky again (i.e. not when just accidentally scrolling down to the current last line).
(yeas I know about column(1)) :-P
What one often has are loglines which are pretty long (i.e. longer then the screen). In this case one can already use -S .
Often one can set up the logs so that fields are separated with a uniqe separator (like tab).
There it would be nice if less could automatically align columns on such separator.
The difference to using something like column would be, that less could align just based on the lengths of the currently shown lines.
Which would mean that if one goes a line up/down it might need to reprint the whole screen, as the newly visible lines might either require larger columns or smaller ones could suffice.
Cheers,
Chris.
The text was updated successfully, but these errors were encountered: