Hi Koichi,
No, the support is still there, but rarely tested (as we do prefer to
use a single style and we add tests for stuff we change now, but did not
have time yet to write it for older stuff like this).
David referred to this as 'dropped', so sorry for the confusion. (We do
not remove features during a release cycle, unless explicitly marked
experimental)
So, if we drop it it will be with version 4 earliest.
regards
Armin
On 15.05.25 11:57, Koichi Murase via FreeRDP-devel wrote:
Hi David,
AFAIK we've dropped intentionally the POSIX style command line, because
we don't want to maintain 2 style of command lines.
Thanks for the information.
Actually, that was one of the possibilities that I initially
suspected, but I couldn't find any information about dropping the
support for the POSIX-style command line based on the web search and
the search on GitHub. I also attempted to search the mailing list
archive, but most of the discussions seemed to be far older than a
point when the POSIX-style command line was clearly supported. Is
there any pointer for dropping the POSIX-style command line (anything
is fine, such as an official announcement, a discussion, or commits
that dropped the POSIX-style command line)?
Maybe it is outdated, but the wiki page [2] mentioned in my first post
still explains that both the POSIX- and Windows-style options are
available.
Also, the current codebase apparently contains the detection of the
POSIX-style and WIndows command lines [8]. What are these codes? Maybe
they are used elsewhere. Or maybe dead codes are maintained within the
codebase.
[8]
https://github.com/FreeRDP/FreeRDP/blob/fa4d99ac5aad0a34f3ad609bf0f664b54cba1cd7/client/common/cmdline.c#L1636-L1639
Based on my observation using the actual binary of xfreerdp [FreeRDP
version 3.12.0 (n/a)] in the Fedora 41 distribution, xfreerdp does
seem to parse some POSIX-style long options. I haven't tested with the
actual remote desktop server, but at least the behavior is different
when I specify existing and non-existing long options such as
"--timeout 100" vs "--timeoutxxx". The former seems to cause a runtime
error, while the latter seems to cause the command-line error. Does
that mean the support for the POSIX-style command line was dropped
after 3.12.0? I don't seem to be able to find anything relevant to it
on the release page, https://github.com/FreeRDP/FreeRDP/releases. Or
is the behavior that I observed some remnants or oversight of the
removed POSIX-style command line?
Based on these observations, my impression is that the support for the
POSIX-style command lines haven't yet been dropped officially, even
though its use doesn't seem to be encouraged very much.
Best regards,
Koichi
_______________________________________________
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel
_______________________________________________
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel
