Having to remember & type a timestamp has much more mental overhead (planning & memory) than "scan/scroll back to last block of vertical whitespace".
That's why suggestions of either named-marks or back-searches aren't considered equally-attractive alternatives to marking the scrollback with a batch of <return>s.
Re:Stop using tail -f (mostly)
by shawabawa3 on Monday March 30, 2015 @03:17PM
(#9291872)
imagine the scenario: "I want to see everything that happens in a single request"
Enter method:
1. Press enter a bunch of times
2. Reload browser
3. Press enter a bunch of times and scroll up
Your method: 1. Search for last line in output to highlight it?
2. Reload page
3. Try and figure out where stuff starts and ends with loads of visual noiseI won't argue that for this specific use case, tail isn't friendlier than less.
But the original poster posted a useful tip, and is now getting aggressive downvotes and comments like "This has nothing to do with what is being discussed in this subthread." I think that's unwarranted.
Re:Stop using tail -f (mostly)
by MadcapJake on Monday March 30, 2015 @04:10PM
(#9292234)
less method:
1. ma
2. Reload browser
3. 'a
less method with two marks: 1. ma
2. Reload browser
3. mb
4. 'aUnfortunately mark doesn't seem to work while you're following.
This trick doesn't work if your log file has a bunch of identical lines and you want to keep an eye on their rate, though.