You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have made a small hack to prettyping which imho renders it way more useful. I leave pp running for hours at a time to watch the performance of the first hop to my (radio) repeater. when I see disruptions (lost packets, long turnarounds) in the history I want to know when they happened; so I added a timestamp at the end of each line.
if ( IS_PRINTING_DOTS ) {
# HACK, add time stamp to end of each line!
printf(system("date \"+ %m.%d.%H:%M\""))
# printf( "\n" )
}
so the end of a typical line for me is now (example):
▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁ 11.02.14:36
unfortunately I don't understand the code quite well enough to make this behave correctly under all circumstances: when the last char of a line is a red bang (lost packet), for some reason I get an extra linefeed and 2 timestamps. the first timestamp is in red (same text formatting as the bang) and then there is a regular (green) timestamp on a line by itself. this is not bothering me much at present :-) since very rarely is there a bang as the last char of the line.
I'd really appreciate it if some future release, someday, had a new flag --timestamp and implemented my crude hack more cleanly so that it doesn't disrupt the output format no matter what the final char of the line is.
The text was updated successfully, but these errors were encountered:
It may be 2022 but as someone who just discovered this program I love this idea. I already have my call for Prettyping to do a new line every two minutes but this would greatly help I think.
I have made a small hack to prettyping which imho renders it way more useful. I leave pp running for hours at a time to watch the performance of the first hop to my (radio) repeater. when I see disruptions (lost packets, long turnarounds) in the history I want to know when they happened; so I added a timestamp at the end of each line.
so the end of a typical line for me is now (example):
▁▁▁▁▁▁▁▁▁▁▁▁▁▁▁ 11.02.14:36
unfortunately I don't understand the code quite well enough to make this behave correctly under all circumstances: when the last char of a line is a red bang (lost packet), for some reason I get an extra linefeed and 2 timestamps. the first timestamp is in red (same text formatting as the bang) and then there is a regular (green) timestamp on a line by itself. this is not bothering me much at present :-) since very rarely is there a bang as the last char of the line.
I'd really appreciate it if some future release, someday, had a new flag --timestamp and implemented my crude hack more cleanly so that it doesn't disrupt the output format no matter what the final char of the line is.
The text was updated successfully, but these errors were encountered: