I normally work in Windows with POV-Ray, but I have access to some big linux
boxes that I'd like to use for my longer renderings.  At the moment I'm trying
to figure out how I can use quickres.ini to set the resolution options, rather
than specifying them individually on the command line, or fixing them within my
scene.ini file.

I updated my copy of quickres.ini to include a section called [default], as well
as a bunch of sections I had added to my windows installation to keep things
consistent.

On the linux box, if I run:

povray $POVHOME/ini/quickres[default] scene.pov

The rendering starts as expected.

povray $POVHOME/ini/quickres[foo] scene.pov

Also works, even though there is no subsection labeled [foo].

povray $POVHOME/ini/quires[160x120, No AA] scene.pov

fails with "Failed to parser command-line option".

I have tried:
'160x120, no AA'
"160x120, no AA"
"160x120,\ no AA"
....

I can't seem to find the magic to allow specifying a section name with embedded
spaces in it.

Do I need to go rename all of the sections in quickres.ini to remove the spaces?


-- Chris R.

Post a reply to this message

hi,

"Chris R" <car### [at] comcastnet> wrote:
> I updated my copy of quickres.ini to include a section called [default],...

disclaimer, I don't use any of the distribution inis.


> On the linux box, if I run:
> ...
> povray $POVHOME/ini/quires[160x120, No AA] scene.pov
>
> fails with "Failed to parser command-line option".
>
> I have tried:
> '160x120, no AA'
> "160x120, no AA"
> "160x120,\ no AA"
> ....

I'd try quote the whole thing.
  $ povray "$POVHOME/ini/quires[160x120, No AA]" scene.pov


the brackets, too, are "special" to the (BASH?) shell.


regards, jr.

Post a reply to this message

On 6/15/23 14:10, jr wrote:
> I'd try quote the whole thing.
>    $ povray "$POVHOME/ini/quires[160x120, No AA]" scene.pov
> 
> 
> the brackets, too, are "special" to the (BASH?) shell.

Try what jr suggested first - and if that doesn't work ->

---
I don't often use ini files, but perhaps the issue related to the file 
names with spaces quoting issue with recent versions of POV-Ray?

See, for example, github issue:

https://github.com/POV-Ray/povray/issues/448

and maybe too :

Message: <6107d751$1@news.povray.org>

or

https://news.povray.org/povray.bugreports/message/%3C6107d751%241%40news.povray.org%3E

Bill P.

Post a reply to this message

William F Pokorny <ano### [at] anonymousorg> wrote:
> On 6/15/23 14:10, jr wrote:
> > I'd try quote the whole thing.
> >    $ povray "$POVHOME/ini/quires[160x120, No AA]" scene.pov
> >
> >
> > the brackets, too, are "special" to the (BASH?) shell.
>
> Try what jr suggested first - and if that doesn't work ->
>
> ---
> I don't often use ini files, but perhaps the issue related to the file
> names with spaces quoting issue with recent versions of POV-Ray?
>
> See, for example, github issue:
>
> https://github.com/POV-Ray/povray/issues/448
>
> and maybe too :
>
> Message: <6107d751$1@news.povray.org>
>
> or
>
>
https://news.povray.org/povray.bugreports/message/%3C6107d751%241%40news.povray.org%3E
>
> Bill P.

Thanks to both of you.  The answer was a combination of quoting the whole thing,
and escaping additional quotes.  Here is what worked:

povray "\"$POVRAY/ini/quickres[160x200, No AA]\"" scene.pov

-- Chris R.

Post a reply to this message

hi,

"Chris R" <car### [at] comcastnet> wrote:
> ... Here is what worked:

out of interest :-),  do apostrophes work, also ?

  $ povray "$POVRAY/ini/quickres['160x200, No AA']" scene.pov

("'$POVRAY/ini/quickres[160x200, No AA]'" too ought "to fly")


regards, jr.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "Chris R" <car### [at] comcastnet> wrote:
> > ... Here is what worked:
>
> out of interest :-),  do apostrophes work, also ?
>
>   $ povray "$POVRAY/ini/quickres['160x200, No AA']" scene.pov
>
> ("'$POVRAY/ini/quickres[160x200, No AA]'" too ought "to fly")
>
>
> regards, jr.

I gave it a try and at least in ksh it seems to work as well.  I thought I had
tried that, but maybe I reversed it and used '"$POVRAY..."'

-- Chris R.

Post a reply to this message