povray 3.5 beta 12 on Linux RH7.2, 320M RAM, on PII 266.

The command line help doesn't seem to work with any of 
the numbers as specified in the man page. 

I've tried:

povray -h0
povray -H0
povray +h0
povray +H0

and tried other numbers too. 

It's asthough it's still looking for an input file name on the command
line. 

--
#local i=.1;#local I=(i/i)/i;#local l=(i+i)/i;#local ll=(I/i)/l;box{<-ll,
-((I/I)+l),-ll><ll,-l,ll>pigment{checker scale l}finish{ambient((I/l)/I)+
(l/I)}}sphere{<i-i,l-l,(I/l)>l/l pigment{rgb((I/l)/I)}finish{reflection((
I/l)/I)-(l/I)specular(I/l)/I}}light_source{<I-l,I+I,(I-l)/l>l/l} // Steve

Post a reply to this message

In article <slr### [at] zero-ppslocaldomain> , Steve 
<ste### [at] zeroppsuklinuxnet>  wrote:

> The command line help doesn't seem to work with any of
> the numbers as specified in the man page.
>
> I've tried:
>
> povray -h0
> povray -H0
> povray +h0
> povray +H0
>
> and tried other numbers too.
>
> It's asthough it's still looking for an input file name on the command
> line.

You are mistaking the image height with help.  Take a look in the manual for
the correct syntax because if the above really is in the man page, the man
page is incorrect.


    Thorsten

Post a reply to this message

On Fri, 08 Mar 2002 14:12:20 -0500, Thorsten Froehlich wrote:

> In article <slr### [at] zero-ppslocaldomain> , Steve
> <ste### [at] zeroppsuklinuxnet>  wrote:
> 
>> The command line help doesn't seem to work with any of the numbers as
>> specified in the man page.
>>
>> I've tried:
>>
>> povray -h0
>> povray -H0
>> povray +h0
>> povray +H0
>>
>> and tried other numbers too.
>>
>> It's asthough it's still looking for an input file name on the command
>> line.
> 
> You are mistaking the image height with help.  Take a look in the manual
> for the correct syntax because if the above really is in the man page,
> the man page is incorrect.

OK, but then so is the Usage function in optout.  "povray -h" still gives
a full usage summary, as does "povray" alone or with "-?" or "-help".
"povray -h[0-7]" doesn't give a subset, as described sketchily in the man
page and in greater detail in the usage summary.  This worked in 3.1g, and
it's easy enough to figure out whether -h[0-7] is the only option, so it
shouldn't be too hard to make it work again.

Now that I poke at it, I see that some of the Unix-specific (mostly
X-related) command-line options aren't working, either.  I'll look into
fixing that for the next beta.

-Mark Gordon

Post a reply to this message

On Fri, 08 Mar 2002 22:13:10 -0500, Mark Gordon wrote:

> OK, but then so is the Usage function in optout.  "povray -h" still gives
> a full usage summary, as does "povray" alone or with "-?" or "-help".
> "povray -h[0-7]" doesn't give a subset, as described sketchily in the man
> page and in greater detail in the usage summary.  This worked in 3.1g, and
> it's easy enough to figure out whether -h[0-7] is the only option, so it
> shouldn't be too hard to make it work again.
> 
> Now that I poke at it, I see that some of the Unix-specific (mostly
> X-related) command-line options aren't working, either.  I'll look into
> fixing that for the next beta.

-h[0-7] told me that it needed an integer so I assumed I was typing the 
command wrong there and didn't include it in the examples I posted.    

Those screens are quite useful in 3.1g so it'll be nice to have them
back. 

--
%HAV-A-NICEDAY                    email mailto:ste### [at] zeroppsuklinuxnet
Steve                                web http://www.zeropps.uklinux.net/
                                             or http://start.at/zero-pps
  2:37pm  up 3 days, 16:35,  1 user,  load average: 1.00, 1.00, 1.00

Post a reply to this message

In article <slr### [at] zero-ppslocaldomain> , Steve 
<ste### [at] zeroppsuklinuxnet>  wrote:

> -h[0-7] told me that it needed an integer so I assumed I was typing the
> command wrong there and didn't include it in the examples I posted.
>
> Those screens are quite useful in 3.1g so it'll be nice to have them
> back.

They are there, just type -h, -help or -? without a number.

    Thorsten

Post a reply to this message

On Sat, 09 Mar 2002 09:42:22 -0500, Steve wrote:
 
> -h[0-7] told me that it needed an integer so I assumed I was typing the
> command wrong there and didn't include it in the examples I posted.

I'm using a Unix shell globbing construction. By "-h[0-7]" I mean "-h0 or
-h1 or ... -h7".  -h alone gives the full usage summary, as Thorsten
mentions, so what's broken currently is the ability to get subsets of the
usage summary.

-Mark Gordon

Post a reply to this message

On Sat, 09 Mar 2002 12:27:11 -0500, Mark Gordon wrote:

> On Sat, 09 Mar 2002 09:42:22 -0500, Steve wrote:
>  
>> -h[0-7] told me that it needed an integer so I assumed I was typing the
>> command wrong there and didn't include it in the examples I posted.
> 
> I'm using a Unix shell globbing construction. By "-h[0-7]" I mean "-h0
> or -h1 or ... -h7".  -h alone gives the full usage summary, as Thorsten
> mentions, so what's broken currently is the ability to get subsets of
> the usage summary.

OK, there's a change in the syntax.  From now on, use -?0, -?1 ....  This
should be less confusing to the user than overloading -h.  The usage
summary and the man page have been updated.

This bug is effectively fixed in the current beta.

-Mark Gordon

Post a reply to this message

On Mon, 18 Mar 2002 20:01:04 -0500, Mark Gordon wrote:
> On Sat, 09 Mar 2002 12:27:11 -0500, Mark Gordon wrote:
> 
>> On Sat, 09 Mar 2002 09:42:22 -0500, Steve wrote:
>>  
>>> -h[0-7] told me that it needed an integer so I assumed I was typing the
>>> command wrong there and didn't include it in the examples I posted.
>> 
>> I'm using a Unix shell globbing construction. By "-h[0-7]" I mean "-h0
>> or -h1 or ... -h7".  -h alone gives the full usage summary, as Thorsten
>> mentions, so what's broken currently is the ability to get subsets of
>> the usage summary.
> 
> OK, there's a change in the syntax.  From now on, use -?0, -?1 ....  This
> should be less confusing to the user than overloading -h.  The usage
> summary and the man page have been updated.
> 
> This bug is effectively fixed in the current beta.

Thanks mark.  Just finished d/ling it 2 minutes ago. 

--
sphere{z*5,1pigment{rgb.5}finish{reflection.3specular.5}}box{<-50,-3,-50>
<50,-2,50>pigment{checker/*\__\\__/  * \_\\__*/scale 2}finish{ambient.7}}
light_source/*__\\__\\__\\__\\__\(    ~ )\__\\__\\__\\__\\*/{<2,5,1>*4,1} 
/*\\__\\__\\__\\__\\__\\__\\__\\__\~  -/__\\__\\__\\__\\__\\*//* Steve */

Post a reply to this message

Mark Gordon <mtg### [at] mailbagcom> wrote:
> OK, there's a change in the syntax.  From now on, use -?0, -?1 ....

  I suppose that you are aware that ? is a wildcard character in most command
line shells, which may cause problems if written as-is (ie. unless you put
the parameter into quotation marks, ie. eg. "-?0").

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

On Tue, 19 Mar 2002 08:33:37 -0500, Warp wrote:

> Mark Gordon <mtg### [at] mailbagcom> wrote:
>> OK, there's a change in the syntax.  From now on, use -?0, -?1 ....
> 
>   I suppose that you are aware that ? is a wildcard character in most
>   command
> line shells, which may cause problems if written as-is (ie. unless you
> put the parameter into quotation marks, ie. eg. "-?0").

OK, I've tested this on a couple of different systems.  Seems to work fine
under sh/bash/ksh (assuming you don't have a file matching that pattern in
.,which seems a reasonable bet), but it breaks under csh/tcsh/zsh:

% echo -?0
echo: No match.

So the problem isn't quite as widespread as first suggested, but it's
still broken.  I'd only tested this under bash, not having considered the
possibility that the shell might have other plans for the '?'.  I agree we
need to continue to offer an alternative to -?[n], and I'm currently
inclined to favor reverting to -h[n].

-Mark Gordon

Post a reply to this message