"Tor Olav Kristensen" <tor### [at] TOBEREMOVEDgmailcom> wrote:
> "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://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
> In Linux/Unix POV-Ray writes to stderr (and perhaps stdout). You can read more
> about redirecting in BASH here:
> NB - What is written here:
> - 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:
I know almost nothing about VS Code, but I have a suspicion that Yong Wang's
answer here is relevant:
It seems to me that his code is dealing with what the executed shell command
outputs to stdout or (and ?) stderr.
Post a reply to this message