POV-Ray : Newsgroups : povray.programming : VSCode Extension - Render Error Output : Re: VSCode Extension - Render Error Output Server Time
27 Nov 2022 20:14:52 EST (-0500)
  Re: VSCode Extension - Render Error Output  
From: Tor Olav Kristensen
Date: 11 Mar 2022 10:15:00
Message: <web.622b67188de14cd87c84c1489db30a9@news.povray.org>
"kennebel" <jac### [at] kennebelcom> wrote:
> Hello there!
>
> I decided to fork the VSCode extension for POV-Ray (which quit working awhile
> back due to changes in the system). I got it back up and running, added a few
> features:
>
> https://marketplace.visualstudio.com/items?itemName=virtual-whirlwind.vscode-povray2
> https://github.com/VirtualWhirlwind/vscode-povray2
>
> While using it on Windows, I've noticed that when there is a scene/syntax issue,
> I need
> to open the regular POV-Ray editor to run the file as the command line rendering
> doesn't give the error message. Is there a 3.7 command line switch/parameter
> that would put the render errors back to the console that I could capture and
> show in the VSCode interface?

A very long time ago I used MicroEmacs in MS DOS v6.22. And then I was able to
make MicroEmacs gather the error messages from the console (when compiling) and
show them in a separate window (IIRC). So I guess that it is still possible in
Windows.

In Linux/Unix POV-Ray writes to stderr (and perhaps stdout). You can read more
about redirecting in BASH here:
https://tldp.org/HOWTO/Bash-Prog-Intro-HOWTO-3.html

NB - What is written here:
https://www.povray.org/documentation/3.7.0/r3_2.html
- indicates that one should be able to write something like this:

cat test.pov | povray +I-

I have tested this in BASH with the POV-Ray available in Ubuntu (20.04 ?), but
unfortunately it does not work.

Also see the comment from c-lipka here:
https://github.com/POV-Ray/povray/issues/35

--
Tor Olav
http://subcube.com
https://github.com/t-o-k


Post a reply to this message

Copyright 2003-2021 Persistence of Vision Raytracer Pty. Ltd.