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
On Thu, Nov 29, 2012 at 10:49 AM, wrote:
> Hi,
>
> I had some discussion with Marc-Andre about logging and error handling
> about two month ago.
>
> My main problem with way it is done in freerdp at the moment, is that a
> GUI user will never see an error message (because it goes to stdout, which
On 02/12/12 19: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.
> ...
> Give it a try and tell me what you think.
I just tested, it works for me, many thanks :-)
Alexis
Hi Gerald,
On 11/29/2012 01:49 PM, rich...@ecos.de wrote:
> My main problem with way it is done in freerdp at the moment, is that a GUI
> user will never see an error message (because it goes to stdout, which you
> might see on Linux if you start from a terminal, but you will never see it on
>
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:[: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 "/"
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 wrote:
> Somehow, running the command does not seem to work for me.
>
> ~/bin/xfreerdp 10.113.131.83:3389
> error: serv
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:
