 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I recently switched from Windows to Linux, and now I finally found time
to set up POV. Everything is fine, but I don't find a "global INI-file"
like the Windows-version has (IMHO it is <POVDIR>/renderer/povray.ini).
This file is parsed before every render, so it's a good place to store
global parameters, line output format, global include paths, etc. Does
the Un*x/Linux version also have such a nice file?
Thanks for your help
Florian
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 04 Dec 2003 12:37:32 -0500, Florian Brucker <tor### [at] torfbold com> wrote:
> I recently switched from Windows to Linux, and now I finally found time
> to set up POV. Everything is fine, but I don't find a "global INI-file"
> like the Windows-version has (IMHO it is <POVDIR>/renderer/povray.ini).
> This file is parsed before every render, so it's a good place to store
> global parameters, line output format, global include paths, etc. Does
> the Un*x/Linux version also have such a nice file?
I don't have much experience with Unix version but I suppose the answer is in
first paragraph of 1.5.2 chapter in your manual.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
~/.povrayrc
--
#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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Does the Un*x/Linux version also have such a nice file?
There are actually two INI files in the UNIX/Linux version
of povray: a system-wide file (usually /usr/local/etc/povray.ini)
and an user file called .povrayrc in your home directory (note: it
is usually "hidden" due to the first dot in its name). The second
file does not exist by default, and you should create it by copying
the first one. If you use a non-root account on your machine (which
is recommanded anyway), you should not touch the system-wide INI file,
but edit your ~/.povrayrc instead.
- NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nicolas Calimet <pov### [at] freefr> wrote:
> (note: it is usually "hidden" due to the first dot in its name)
It's debatable whether a file can be called "hidden" simply because
ls doesn't list it by default.
I'm not aware of any other program which would not "see" it as any
other file. Even "echo *" lists all files.
--
#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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I don't have much experience with Unix version but I suppose the answer is in
> first paragraph of 1.5.2 chapter in your manual.
You're right. I did check the other sections of the manual (those about
INI-options), but I didn't even know there was a platform specific
section...
Thanks for the help!
Florian
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 04 Dec 2003 15:16:23 -0500, Warp wrote:
> I'm not aware of any other program which would not "see" it as any
> other file. Even "echo *" lists all files.
Nautilus' default configuration (in fact, most of GNOME's default
configuration; I can't speak for KDE) is to hide .files and .directories.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3fcf9617@news.povray.org>, Warp <war### [at] tagpovrayorg>
wrote:
> Nicolas Calimet <pov### [at] freefr> wrote:
> > (note: it is usually "hidden" due to the first dot in its name)
>
> It's debatable whether a file can be called "hidden" simply because
> ls doesn't list it by default.
> I'm not aware of any other program which would not "see" it as any
> other file. Even "echo *" lists all files.
It *is* a convention that files beginning with "." are considered
invisible. "echo *" doesn't list all the files, it echos a string of all
files matching "*" to standard output...dot files match that expression,
so they are included.
--
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tagpovrayorg
http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Christopher James Huff <cja### [at] earthlinknet> wrote:
> "echo *" doesn't list all the files, it echos a string of all
> files matching "*" to standard output
The difference being...?-)
--
#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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3fd09089@news.povray.org>, Warp <war### [at] tagpovrayorg>
wrote:
> Christopher James Huff <cja### [at] earthlinknet> wrote:
> > "echo *" doesn't list all the files, it echos a string of all
> > files matching "*" to standard output
>
> The difference being...?-)
Visibility has nothing to do with matching regular expressions...unless
you set up the expression to depend on a leading dot. (though I do think
this method is stupid...a meta-data flag would be far more appropriate)
--
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tagpovrayorg
http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
