Hey! I'm ok with adding a manpage, but I personally don't use them and wouldn't know where to start when adding one.

I'm more than happy to accept even a half-baked manpage from you, to get us started?

I'll work on it tomorrow

There is clap_mangen which supposedly makes it very easy to generate it from the source code.

This is my draft: manpage.md
I'm not sure what values --interface takes. Also please think about generating it with clap-mangen (or similar crates) in case the options/syntax/whatever changes.

Thank you! If you could create a pull request with that, I'll approve and merge it now. I have a release that's coming out soon as well.

I can automate the manpage at a later date, thank you for the research!

see #253

I checked the draft and have an enhancement request for it. Can definitions for the abbreviations in gping's output be added to the manpage?

Asking because it would clear up any uncertainties or misunderstandings about what each field in indicating.

(Initially I was unsure about what the p95 and t/o fields are indicating, but now after googling I assume p95 to mean 95% of ping times have lower latency than the reported p95 time, and that t/o is the number of pings that have timed out since the graph started.)
By the way this is a awesome app!! Thank you.

I tried to add clap-mangen in #257, but I'm not really happy with it. I'll try and revisit it.

With regards to adding t/o and p95 to the manpage, sure, but I'm not really sure how 😅. I'll take a look when I have time next week.

I'm going to close this for now as #253 is merged. thanks for the help @werdahias <3

@werdahias is there any movement on the gping Debian package? Anything I can help with?