2011/8/26 Mike Gilbert :
> On Fri, Aug 26, 2011 at 5:24 PM, Nils Andresen wrote:
>> 2011/8/26 Mike Gilbert :
>>> Why not just use argv[0]?
>> I was under the impression that in c (as in c#) you don't get the
>> clients name in the args.
> In C, argv[0] normally contains the name of the program bei
On Fri, Aug 26, 2011 at 5:24 PM, Nils Andresen wrote:
> 2011/8/26 Mike Gilbert :
>> Why not just use argv[0]?
>
> Hmm. I am mainly a c# programmer trying to get my bearings around c
> but I was under the impression that in c (as in c#) you don't get the
> clients name in the args.
> Or are you sug
2011/8/26 Mike Gilbert :
> Why not just use argv[0]?
Hmm. I am mainly a c# programmer trying to get my bearings around c
but I was under the impression that in c (as in c#) you don't get the
clients name in the args.
Or are you suggesting to push the clients name in the args? I.e.
expecting the cl
On Fri, Aug 26, 2011 at 5:03 PM, Nils Andresen wrote:
> now:
> args.c is used in xfreerdp and dfreerdp. Help should print something like
> Usage: [d|x]freerdp [options] server:port
> is there a cool way to determine the client that uses args.c, or
> should freerdp_parse_args get one more paramete
Hi,
I wanted to add a nice help-text to libfreerdp-utils/args.c but I ran
into a few problems. Some of which I simply need some input from you.
One - I'll need a good idea...
first the simple things:
- what does --no-auth do?
- what does --no-fastpath do?
- what does --rfx do?
now:
args.c is used
