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