Use -l (raw mode) same as -p (split) mode

[eakteam]

@rewolff I'm stilll stucked 😆 ....

Now the -p (split) mode works perfectly but since it uses snprintf nothing writes to stdout and I'm unable to read data from shell process using inputstreamreader from Android in my case....

The -l (raw) mode works OK in my case but it doesn't display same data as split mode :

This is how split mode displays

snprintf(newLine, sizeof(newLine), "%s %d %d %d %.1f %.1f %.1f",
         name, net_loss(at), net_returned(at), net_xmit(at),
         net_best(at) / 1000.0, net_avg(at) / 1000.0,
         net_worst(at) / 1000.0);

But if i change snprintf to printf and after fflush(stdout); it fill screen with random data without ordering or something, just can't use it that way...

Can you please help me how to make -l (--raw) mode modify to display the same data like in the same line:

position, host, net_loss, net_returned, net_xmit, net_best, net_avg, net_worst ...... etc.

I really need help for one project of mine but can't write C code myself and i have 15 days strugling with it 😆 .....

[rewolff]

When something changes, the split mode will "render" all of the lines to internal memory and only print those lines that have changed since last time. That's the stuff with snprintf. Raw just printfs stuff and fflush. And split does the same.

And with a direct "printf ... ", you might think that printf might print a number, and then a string and... so on. But internally printf prints to a buffer and outputs the whole line.

But in the split mode code we "render" the whole line and then print it in one go. If you're getting mixups, I don't know what's going on. It seems to me as if you're not running the code that I'm looking at.

[eakteam]

@rewolff I mean that split mode displays items OK in terminal but when trying to read stdout from Java/Kotlin Process InputStreamReader it doesn't print anything, in other case raw mode is printing data OK at InputStreamReader.

[rewolff]

As I said before, both the code in raw.c and split.c use printf to write the data to stdout and then "fflush (stdout)" to make sure it doesn't get buffered and you can get the results immediately. You will have to debug why things go wrong. I'm out of guesses.