 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich wrote:
>
> In article <3C3DA175.4B246EAC@chez.com> , "Thierry B." <oul### [at] chez com>
> wrote:
>
> > with +Iawk1 -without space- pov start happily, but this
> > break (for me) a _lot_ of Makefiles and shells scripts.
>
> This is correct. The +I with a space between the name and switch was never
> officially supported or documented nor will be be officially documented or
> supported in the future. Sorry!
>
Argh:)
but if I look at pov138.htm in 3.1 doc, this was not specified
that there must be NO space betwen optkey and optarg...
--
Thierry exposant de trucs bizarres http://la.buvette.org/exPOV/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3C3DB995.2D20A8C0@chez.com> , "Thierry B." <oul### [at] chezcom>
wrote:
> Argh:)
> but if I look at pov138.htm in 3.1 doc, this was not specified
> that there must be NO space betwen optkey and optarg...
The documentation does not tell you that "skyscraper", "tree" or "computer"
are invalid keywords either :-)
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich <tho### [at] trfde> wrote:
:> with +Iawk1 -without space- pov start happily, but this
:> break (for me) a _lot_ of Makefiles and shells scripts.
: This is correct. The +I with a space between the name and switch was never
: officially supported or documented nor will be be officially documented or
: supported in the future. Sorry!
However, you can run it now *without* the +I (as long as you give the full
filename, ie the '.pov' part included).
That is: povray file.pov
--
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Jeudi 10 Janvier 2002 17:28, Thorsten Froehlich wrote:
> In article <3C3DB995.2D20A8C0@chez.com> , "Thierry B."
> <oul### [at] chezcom> wrote:
>
>> Argh:)
>> but if I look at pov138.htm in 3.1 doc, this was not specified
>> that there must be NO space betwen optkey and optarg...
>
> The documentation does not tell you that "skyscraper", "tree" or
> "computer" are invalid keywords either :-)
But I see no reason they would be, while I see reasons spaces
would be allowed between +l and its argument: the vast majority
of Unix programs accept that.
--
spa### [at] freefr
You have my name and my hostname: you can mail me
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Jeudi 10 Janvier 2002 14:26, Mark Gordon wrote:
> Just in time to expire in a few days, but I should have an
> update available concurrent with other platforms.
Thank you!
> Built on Red Hat 7.2, in case it matters.
I don't know. What did Red Hat screw up, this time?
> They'll be built with an prefix of
> /usr, but this
> one is built with a prefix of /usr/local, though, so as not to
> conflict with
> anything you have in package management.
I hope there will still be a way to have a .tar.gz installed in
/usr/local. I won't install software elsewhere.
> Keep a mind to your
> $PATH if you end up with multiple versions installed in
> different prefixes at some point.
$ which povray
--
spa### [at] freefr
You have my name and my hostname: you can mail me
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <181### [at] mayaboanet> , Adrien Beau
<spa### [at] freefr> wrote:
>>> Argh:)
>>> but if I look at pov138.htm in 3.1 doc, this was not specified
>>> that there must be NO space betwen optkey and optarg...
>>
>> The documentation does not tell you that "skyscraper", "tree" or
>> "computer" are invalid keywords either :-)
>
> But I see no reason they would be, while I see reasons spaces
> would be allowed between +l and its argument: the vast majority
> of Unix programs accept that.
POV-Ray is not a Unix only program. The command line works the same
everywhere and only the i switch ignored a space before the actual filename,
all other switches always worked only as described in the manual.
Doing what Warp suggested is an option you have, and it is only one
character more to type, while of course without the space you have to type
one character less than before. There is no problem here and I see no need
to argue about it.
Thorsten
____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg
I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
The previous man page was ambiguous; I'm not sure whether the error is mine.
I'll check the 3.0.2 man page at some point. In any event, the syntax is
clarified in the current man page.
-Mark Gordon
In article <3c3db458@news.povray.org>, "Thorsten Froehlich"
<tho### [at] trfde> wrote:
> In article <3C3DA175.4B246EAC@chez.com> , "Thierry B." <oul### [at] chezcom>
> wrote:
>
>> with +Iawk1 -without space- pov start happily, but this break (for
>> me) a _lot_ of Makefiles and shells scripts.
>
> This is correct. The +I with a space between the name and switch was
> never officially supported or documented nor will be be officially
> documented or supported in the future. Sorry!
>
> Thorsten
>
> ____________________________________________________ Thorsten Froehlich
> e-mail: mac### [at] povrayorg
>
> I am a member of the POV-Ray Team.
> Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <135### [at] mayaboanet>, "Adrien Beau"
<spa### [at] freefr> wrote:
> On Jeudi 10 Janvier 2002 14:26, Mark Gordon wrote:
>
>> Just in time to expire in a few days, but I should have an update
>> available concurrent with other platforms.
>
> Thank you!
>
>> Built on Red Hat 7.2, in case it matters.
>
> I don't know. What did Red Hat screw up, this time?
I don't know that they screwed up anything. Mostly it's a hint to users
to let me know what they're running if they report bugs. ;-)
>> They'll be built with an prefix of
>> /usr, but this
>> one is built with a prefix of /usr/local, though, so as not to
>> conflict with
>> anything you have in package management.
>
> I hope there will still be a way to have a .tar.gz installed in
> /usr/local. I won't install software elsewhere.
Yeah, anything I build that isn't intended for use with a formal package
management system will be built with a /usr/local prefix. povlinux.tgz
isn't going away completely.
>> Keep a mind to your
>> $PATH if you end up with multiple versions installed in different
>> prefixes at some point.
>
> $ which povray
Precisely.
-Mark Gordon
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich <tho### [at] trfde> wrote:
: Doing what Warp suggested is an option you have, and it is only one
: character more to type, while of course without the space you have to type
: one character less than before.
The main problem of "+Ifile" and the biggest advantage of "file.pov" is
that the filename completion of most shells works in the latter case but not
in the former. This means that in the latter case you only need to type 2-3
keystrokes which in the former you need to type a lot more.
This wasn't a problem before because you could leave a space between the +I
and the filename, and so the filename completion worked.
--
#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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
>
> The main problem of "+Ifile" and the biggest advantage of "file.pov" is
> that the filename completion of most shells works in the latter case but not
> in the former. This means that in the latter case you only need to type 2-3
> keystrokes which in the former you need to type a lot more.
> This wasn't a problem before because you could leave a space between the +I
> and the filename, and so the filename completion worked.
Doesn't bash allow to configure the auto-completion so it will recognize
this correctly?
--
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other
things on: http://www.schunter.etc.tu-bs.de/~chris/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
