Unable to set ping wait interval on OS X

[thinkspill]

Setting the interval with -i5 works with regular ping (5 seconds between pings), but the same flag passed to gping throws duplicated error messages:

[ ~ ]$ python3 --version
Python 3.5.0
[ ~ ]$ ping -i5 google.com
PING google.com (216.58.192.14): 56 data bytes
64 bytes from 216.58.192.14: icmp_seq=0 ttl=53 time=44.896 ms
64 bytes from 216.58.192.14: icmp_seq=1 ttl=53 time=36.484 ms
^C
--- google.com ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 36.484/40.690/44.896/4.206 ms
[ ~ ]$ gping -i5 google.com
usage: ping [-AaDdfnoQqRrv] [-b boundif] [-c count] [-G sweepmaxsize]
            [-g sweepminsize] [-h sweepincrsize] [-i wait] [−k trafficclass]
            [-l preload] [-M mask | time] [-m ttl] [-p pattern]
            [-S src_addr] [-s packetsize] [-t timeout][-W waittime] [-z tos]
            host
       ping [-AaDdfLnoQqRrv] [-b boundif] [-c count] [-I iface] [-i wait]
            [−k trafficclass] [-l preload] [-M mask | time] [-m ttl] [-p pattern] [-S src_addr]
            [-s packetsize] [-T ttl] [-t timeout] [-W waittime]
            [-z tos] mcast-group
[ ~ ]$

[orf]

Hi, currently only the first parameter is passed to the ping process (hence the error message). Thinking about it now that seems stupid, we might as well pass all gping arguments to the underlying ping process. I'll fix that later :)

[thinkspill]

👍 Thanks!

I'm surprised graphical ping plotters are not more popular. They are fantastic for quickly determining if your internet connection problem is local or external, for those of us who need to worry about that sort of thing. :) Thanks for writing yours!

[ghost]

@orf What about going the _"UNIX Way"_ ?

Instead of passing every argument to ping/gping you could let the user decide using a double-dash.
This way, you could also implement gping options (like being more verbose
or turning the colors off).

Example:

gping --verbose --no-color -- -i5