fix database user input flag about tcping HOT 8 CLOSED

got it sorry for over complicating things..

thanks to @luca-patrignani the issue is resolved

Not a problem at all mate. I am grateful for your contributions!

from tcping.

hi @pouriyajamshidi
Thanks for the mention 😃.
Can you please describe the func?

from tcping.

Hi @wizsk,

I am willing to hear your proposal to modify the permuteArgs func. If it proves to be a small change, we can forfeit moving to Cobra for now and save us some work.

from tcping.

ok @pouriyajamshidi I will let you know

from tcping.

hey @pouriyajamshidi
Why can't we do something like this?

	// arg 1 and 2 is reserved for url and port
	url := os.Args[1]
	port := os.Args[2]

	// we can parse the rest
	os.Args = os.Args[2:]
	flag.Parse()

I'm ignoring the error handling
for the -u flag we can add some extra logic

from tcping.

You want to preserve this functionality

		{
			"host/ip before option",
			args{args: []string{"127.0.0.1", "8080", "-r", "3"}},
			[]string{"-r", "3", "127.0.0.1", "8080"},
		},
		{
			"host/ip after option",
			args{args: []string{"-r", "3", "127.0.0.1", "8080"}},
			[]string{"-r", "3", "127.0.0.1", "8080"},
		}

this is why everything is getting all over the place

from tcping.

well, to be frank, that is how all other OS utilities work. The order in which you provide the flags never matters.

from tcping.

got it sorry for over complicating things..

thanks to @luca-patrignani the issue is resolved

from tcping.