|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I use an editor to write Povray scripts and run the renders with a
command shell that looks like :
'megapovplus +i% +w320 +h240 -l/mnt/dd1/image/pov >& /dev/null'
I did this because a new window is created with when a render is
completed. I ended up with lots of window on my desk(top).
The point is that when errors are detected, nothing is shown. I wanted
to use the 'Fatal_Error_Command', but it cannot be used in the command
line. If I put this command in a ini files, how do I tell POV to show
the Fatal_File stream in a new window ? If possible, I'd like to have
the same window for all the errors : No new window created when a new
error is detected.
The answer is surely simple, but I am still shiny new in the Linux
world.
Would you advise something else ?
Thanks
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Would you advise something else ?
I'll look into this.
-Mark Gordon
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thanks for that.
I am interested in any solution
It seems that I leave you some work these days. ( header files).
Cheers
>
> > Would you advise something else ?
>
> I'll look into this.
>
> -Mark Gordon
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
<ffj### [at] club-internetfr> wrote:
> The point is that when errors are detected, nothing is shown. I wanted
> to use the 'Fatal_Error_Command', but it cannot be used in the command
> line. If I put this command in a ini files, how do I tell POV to show
> the Fatal_File stream in a new window ? If possible, I'd like to have
> the same window for all the errors : No new window created when a new
> error is detected.
I am not exactly sure if this will do what you want, but why not redirect
all _other_ streams to /dev/null using the Xxx_File option in an INI file,
and only leave Fatal_File stream as is. Your shell can then capture the
output and do what it wants with it.
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I think that what I am going to do for the time being.
Thanks for the tip.
I am wondering : Do all the unices-POVers use Emacs to edit their scenes?
If not, what do they use ?
Fabien
> <ffj### [at] club-internetfr> wrote:
>
> > The point is that when errors are detected, nothing is shown. I wanted
> > to use the 'Fatal_Error_Command', but it cannot be used in the command
> > line. If I put this command in a ini files, how do I tell POV to show
> > the Fatal_File stream in a new window ? If possible, I'd like to have
> > the same window for all the errors : No new window created when a new
> > error is detected.
>
> I am not exactly sure if this will do what you want, but why not redirect
> all _other_ streams to /dev/null using the Xxx_File option in an INI file,
> and only leave Fatal_File stream as is. Your shell can then capture the
> output and do what it wants with it.
>
> 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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>
> I think that what I am going to do for the time being.
> Thanks for the tip.
>
> I am wondering : Do all the unices-POVers use Emacs to edit their scenes?
> If not, what do they use ?
>
> Fabien
Andreas Dilger used vi, IIRC. I use Emacs.
-Mark Gordon
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>
>I am wondering : Do all the unices-POVers use Emacs to edit their scenes?
>If not, what do they use ?
Some use Pico, some use Nedit and even MCedit. There was a thread
above where many people gave answers to this question.
I did use Pico, but now use emacs.
--
Cheers
Steve email mailto:ste### [at] zeroppsuklinuxnet
%HAV-A-NICEDAY Error not enough coffee 0 pps.
web http://www.zeropps.uklinux.net/
or http://start.at/zero-pps
11:17am up 25 days, 9:44, 2 users, load average: 2.32, 2.18, 2.08
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Steve <ste### [at] zeroppsuklinuxnet> wrote:
: I did use Pico, but now use emacs.
That's the spirit! :)
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):_;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
>
> Steve <ste### [at] zeroppsuklinuxnet> wrote:
> : I did use Pico, but now use emacs.
>
> That's the spirit! :)
I use vim.
I'm in the process of (hopefully) vastly
ameliorating [poor english? -- sorry]
its POV-Ray support.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Who uses nedit here ?
I did its syntax highlighting for POV in 15 minutes. There are still a
few keywords to add, but it works amazingly well.
Fabien
> Warp wrote:
> >
> > Steve <ste### [at] zeroppsuklinuxnet> wrote:
> > : I did use Pico, but now use emacs.
> >
> > That's the spirit! :)
>
> I use vim.
>
> I'm in the process of (hopefully) vastly
> ameliorating [poor english? -- sorry]
> its POV-Ray support.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |