On Tue, Dec 4, 2012 at 5:00 PM, Marc-André Moreau < marcandre.mor...@gmail.com> wrote:
> Hi, > > As explained earlier, the new command-line options are first based on the > mstsc options, from which we extend to add all our options. > > You can find the mstsc command-line reference here: > > http://windows.microsoft.com/en-US/windows-vista/Use-command-line-parameters-with-Remote-Desktop-Connection > > mstsc [<connection file>] [/v:<server[:port]>] [/admin] [/f[ullscreen]] > [/w:<width>] [/h:<height>] [/public] | [/span] [/edit "connection file"] > [/migrate] [/?] > > Since we support both syntaxes, /v becomes -v > > Using an option for the hostname means we can put the hostname anywhere we > want in the command. > Why base it on mstsc at all? do we/you really want FreeRDP to be a mstsc clone? I think this is wrong. And i strongly believe that a option for hostname is wrong, (And I do use mstsc and it's options, and have always gone mad on it in Windows as well) If need be use a option for the rdp file instead. Of course there is pros and cons to everything, and the biggest con being changing a existing and working interface. If this was done when FreeRDP was redone from scartch that would have been fine, but now there is a strong need for backwards compability on the command line. > > With mstsc, the only option-less argument that can be passed is the .rdp > connection file. If we were to retain the old syntax where the hostname is > always the last argument and option-less, then we would not be able to > really make the difference between xfreerdp being invoked with a .rdp file > and xfreerdp being invoked with a hostname, unless we check for the .rdp > file extension. > Do we need to? (see above) Supporting rdp files is nice, but can be done as a option. Some logic can be used to get most cases, ofcourse if we use a option we won't need to but still it is possible. Some idéas: A option with / in it is probably a rdp file, (unless it is a http ts gw? so check for http:?) if it ends with .rdp it is probably a config file If it contains : it is probably a hostname, if it is likely to be a rdp file check if it exists, if not try to use it as hostname. > > Now you do bring a point that since putting the hostname last is no longer > enforced, this breaks the old functionality where multiple command lines > could be passed once to xfreerdp to launch multiple instances. It would be > possible to use some sort of a separator to divide set of options and > provide similar functionality. However, I'd like to know more about who, > why and how this feature was used exactly, and if we should do it the same > way (multiple set of options in a single command-line that can only be > entered once). What happens if you want to launch another session from the > same instance after it has already been launched? > Here I agree who used it to what? > > Here is what I suggest as a replacement or addition: > > Add a command-line argument giving the path to a local named pipe like > /tmp/freerdp, on which the given xfreerdp instance would listen for further > command-line strings. We could also make it such that xfreerdp could be ran > without launching a session, and just listen for connection command lines. > > What do you think? > Someone might need this but I don't, it would be interesting to hear if anyone does and it sounds like a good approach. (maybe should be taken up in a separate conversation?) I still think that since freerdp is mainly a client then it needs to just take the hostname. I go mad on clients like mysql where you need to add hostname with a option prefixed. In some cases it might make sens, but in most it doesn't! xfreerdp -globalopt1 -globalopt2 host1:3389 -opt-for-host1 host2:3399 -opt-for-host2 Is still my request for supported syntax. in this case hostname will be supported anywhere on the line. (at least if only one) Removing support for the multihost is also fine for me, as said above, who is using it? And that is also something that many new users get wrong by adding options after hostname. Once again, please keep backwards compability for options, there will be many users who have scripts, shortcuts, or alias that they will want to continue to use! You may add obsolete warnings so that users can migrate, but it will take some time before they may be removed. > On Tue, Dec 4, 2012 at 10:34 AM, Christian Nilsson <nik...@gmail.com>wrote: > >> Why do we need to add -v before hostname? >> Is it it still needed to have host as the last option on the commandline? >> >> There is other applications that can take them in any order (mplayer is >> one example i have mentioned before) >> Is there still multi connection support as in FreeRDP-old (one instance >> of xfreerdp connected to multiple servers) If not giving commands in any >> order should be trivial? And even if there is multi connections support it >> shuld work with a command like: xfreerdp -globalopt1 -globalopt2 host1:3389 >> -opt-for-host1 host2:3399 -opt-for-host2 >> >> This -v option dosn't make sense to me. >> >> Regards >> Christian >> >> On Tue, Dec 4, 2012 at 8:19 AM, Kevin Dalley <kdal...@vmware.com> wrote: >> >>> OK. I understand it a little bit more. I hadn't realized that the >>> server name and port are now optional, >>> rather than mandatory. I tested the new parser briefly. There do seem >>> to be a lot of changes. >>> It will take me a while to determine whether I understand it and can use >>> it. >>> >>> Some suggestions: >>> >>> If file is optional, then it should have an option in front of it, >>> otherwise it should be >>> mandatory. >>> >>> Test this parser for quite a while before switching to it in stable. >>> >>> There are very reliable CLI parsers already written. Writing a new one >>> brings a strong risk that there are some cases which are not interpreted >>> correctly. >>> >>> Here's a case which seems to be interpreted incorrectly. >>> Since the file name starts with "/", the parser assumes that we >>> are using windows style options. >>> >>> $ xfreerdp /tmp/foo -v 10.113.138.75:3389 >>> error: server hostname was not specified with /v:<server>[:port] >>> >>> ----- Original Message ----- >>> From: Marc-André Moreau <marcandre.mor...@gmail.com> >>> To: Kevin Dalley <kdal...@vmware.com> >>> Cc: Alex Bligh <a...@alex.org.uk>, Freerdp-devel < >>> freerdp-devel@lists.sourceforge.net>, Alexis Moinet < >>> alexis.moi...@umons.ac.be> >>> Sent: Mon, 03 Dec 2012 20:15:41 -0800 (PST) >>> Subject: Re: [Freerdp-devel] Why is there a change in the command line >>> interface? >>> >>> Hey, I haven't magically brought back the old *options* back, only the >>> syntax. >>> Your command should be: >>> xfreerdp -v 10.113.131.83 >>> >>> On Mon, Dec 3, 2012 at 6:31 PM, Kevin Dalley <kdal...@vmware.com> wrote: >>> Somehow, running the command does not seem to work for me. >>> >>> >>> ~/bin/xfreerdp 10.113.131.83:3389 >>> >>> error: server hostname was not specified with /v:<server>[:port] >>> >>> >>> I see a potential problem with >>> >>> >>> freerdp_detect_windows_style_command_line_syntax >>> >>> >>> If any of the arguments are a file name which starts with a "/", then >>> the command line would be assumed to be >>> >>> windows style. >>> >>> >>> ----- Original Message ----- >>> >>> From: "Alex Bligh" <a...@alex.org.uk> >>> >>> To: "Marc-André Moreau" <marcandre.mor...@gmail.com> >>> >>> Cc: "Alex Bligh" <a...@alex.org.uk>, "Kevin Dalley" <kdal...@vmware.com>, >>> "Freerdp-devel" <freerdp-devel@lists.sourceforge.net>, "Alexis Moinet" < >>> alexis.moi...@umons.ac.be> >>> >>> >>> Sent: Sunday, December 2, 2012 11:58:47 PM >>> >>> Subject: Re: [Freerdp-devel] Why is there a change in the command line >>> interface? >>> >>> >>> On 2 Dec 2012, at 18:41, Marc-André Moreau wrote: >>> >>> >>> > I have added support for both syntaxes. Detection of the syntax is >>> >>> > performed by checking if arguments start with / or not. >>> >>> > >>> >>> > Right now the help will show only the windows-style syntax, but the >>> >>> > arguments are exactly the same for the other syntax, aside from the >>> syntax >>> >>> > itself. >>> >>> >>> You could always display windows help from /help and POSIX help from >>> --help. >>> >>> >>> -- >>> >>> Alex Bligh >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial >>> Remotely access PCs and mobile devices and provide instant support >>> Improve your efficiency, and focus on delivering more value-add services >>> Discover what IT Professionals Know. Rescue delivers >>> http://p.sf.net/sfu/logmein_12329d2d >>> >>> _______________________________________________ >>> Freerdp-devel mailing list >>> Freerdp-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/freerdp-devel >>> >> >> > ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
