We have discussed whether a unified configuration model for tlclient would be a good idea. This idea is basically that all options should be settable either from the tlclient.conf file, from the command line or from the GUI in ascending priority order. Thus, if the sysadm wants, he/she should be able to actually set both user and password in the config file and also stuff that is controlled only by the -l (GUI lock) option today.
*** Bug 3534 has been marked as a duplicate of this bug. ***
See also bug 3555.
We've also had requests for reading configurations from a network - LDAP, HTTP, w/e. Do we consider this interesting of the ThinLinc client or do we believe that distributing a special configuration file to all clients is something that the client operating system should provide tools for?
Let's make this a bit more specific rather than everything that could be improved with the configuration. This bug is now specifically about command line options.