Hi, I think it is ok to shorten the command-line options.It is a correct presupposition that the user should not have to care about the details of the program's working, as for example which shared objectfiles to load. The commandline options should be about which goals to reach, for example forwarding of local home dir. Then: to get rid of commands for sub-plugin-loading is fine. The commandline options should be easy to understand and remember.
In my opinion either "/a" nor "--plugin rdpr etc..." is easily understood and remembered. I would say that "--drive=<remote drive>,<local dir>" is. What relation is there between "a" and drive, disk or dir? I think that the options should use the standard of one hyphen for one-letter options, and two hyphens for more-than one letter options. I see is no significant gain in leaving this part of the standard. The problem with + and - then could could be solved with two sets of options: --enable-this and --disable-this. Or like the options to configure: --enable-this=off The quantum of typing is no big deal. Deviating too far from the posix standard is. Olav. ------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: INSIGHTS What's next for parallel hardware, programming and related areas? Interviews and blogs by thought leaders keep you ahead of the curve. http://goparallel.sourceforge.net _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel