The remaining question for the still open FlySpray issue 214 was whether 
to better document which of the old X11 flags no longer functioned due 
the use of the Simple DirectMedia Library for display.

The last comment was:

Comment by Grimbert Jérôme (Le_Forgeron) - Friday, 09 December 2011, 
14:28 GMT+5

 From my point of view, the original issue is closed (as now with #5460, 
the offending line would be dumped, the detection of forgotten alias or 
magic macro should be trivial).

The part about the Wiki of Unix options is still open: 3.7 use the SDL 
library, which does not intercept the X11 setting. so -display, -icon 
and so on are not supported. Supported specific options are in the unix 
specific source file (from memory: -help, -version; and their shortcuts).

-display and al. were supported at least in 3.1, and that was before SDL 
library. I do not know when the change occurred (3.5, 3.6, or 3.7)

----------

See: 
http://wiki.povray.org/content/Documentation:Unix_Section_6#Understanding_POV-Ray_Options

In my testing of the listed special unix options do the following:

-display <display_name>  --> Will fail with a command line parse error 
so long as a display name is given. +-display otherwise acts like +-D.

-geometry [WIDTHxHEIGHT][+XOFF+YOFF] --> Fails with a command line parse 
error.

-help --> Works fine.

-icon --> Fails due the -i being seen as specifying a scene file name 
con, unless the scene file comes after -icon in which case things run 
without complaint.

-title <title> --> Fails with a command line parse error.

-visual <visual_type> --> Fails with a command line parse error if a 
visual_type is specified and runs without complaint otherwise.

I've closed the issue and the information above can be added to the 
documentation - or not. My personal opinion is we probably should add at 
least a sentence saying explicitly not all the listed X11 supported 
options will work as expected - something the known bugs link implies 
but doesn't say outright.

I'll be closing the issue with a comment pointing to this thread.

Bill P.

Post a reply to this message