Thorsten Froehlich wrote:
> Anders K. wrote:
>> From the docs, section 5.1.2  Using INI Files:
>>
>> Note: although the term 'INI file' is used by POV-Ray, this was
>> implemented before the widespread acceptance of Microsoft Windows, and
>> while POV-Ray's INI files are almost identical to those of Windows, there
>> are some minor differences (the foremost being that it is legal to have
>> multiple instances of the same item in a section). INI files are used on
>> all platform versions of POV-Ray, not just on the Windows platform
> 
> It says nothing about povray.ini being read at startup, does it? 

It doesn't, but:
There's a povray.ini in povray35 (and if there isn't, POV-Ray generates a 
warning).
The windows version uses povray.ini, so the unix version should do so, too.

> Actually, it can't because that is a platform specific thing, so:

Why? There's no problem having a povray.ini on any system (AFAIK at least).

> The Unix documentation however, does still call the file povray.ini while
> it should say povray.rc...

When do people learn that Unix doesn't need those stupid windows 
extensions? ;) The file is called ".povrayrc".
README.unix says:

   The default povray.ini file that is shipped with the Unix archive
   assumes that POV-Ray will be installed under /usr/local/lib/povray31.
   If you are not installing POV-Ray there, you should edit the
   Library_Path specifications in this file to point to the location
   where POV-Ray is installed.  Each user should copy this file to
   ".povrayrc" in their home directory.

So it's not a bug that POV-Ray doesn't read povray.ini if there's .povrayrc 
in home directory, but it's IMO not the expected behavior. I think it might 
really be a better solution to read .povrayrc *and* povray.ini because 
otherwise the user probably would have to copy povray.ini. The 
configuration in povray.ini makes much more sense than (some of) POV-Ray's 
default values.

BTW, README.unix (and maybe README, too) have to be UPDATED!
-- 
Felix Wiemann

Post a reply to this message