POV-Ray : Newsgroups : povray.programming : VSCode Extension - Render Error Output Server Time
28 May 2022 12:17:45 EDT (-0400)
  VSCode Extension - Render Error Output (Message 1 to 9 of 9)  
From: kennebel
Subject: VSCode Extension - Render Error Output
Date: 4 Mar 2022 19:20:00
Message: <web.6222ab8d92d88b32ace99571a96b55c3@news.povray.org>
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?


Post a reply to this message

From: jr
Subject: Re: VSCode Extension - Render Error Output
Date: 5 Mar 2022 02:55:00
Message: <web.622316498de14cd8ed36e5cb6cde94f1@news.povray.org>
hi,

"kennebel" <jac### [at] kennebelcom> wrote:
> ... 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?

<https://wiki.povray.org/content/Reference:Text_Output_Options>

(no idea re "VSCode interface")


regards, jr.


Post a reply to this message

From: kennebel
Subject: Re: VSCode Extension - Render Error Output
Date: 10 Mar 2022 18:55:00
Message: <web.622a8eca8de14cd8ace99571a96b55c3@news.povray.org>
"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> "kennebel" <jac### [at] kennebelcom> wrote:
> > ... 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?
>
> <https://wiki.povray.org/content/Reference:Text_Output_Options>
>
> (no idea re "VSCode interface")
>
>
> regards, jr.

Thanks for the response. No matter what I try with the settings suggested there,
nothing ever seems to change during my renders. So sad. Makes building
supporting apps challenging. :)


Post a reply to this message

From: jr
Subject: Re: VSCode Extension - Render Error Output
Date: 11 Mar 2022 00:20:00
Message: <web.622adacd8de14cd8ed36e5cb6cde94f1@news.povray.org>
hi,

"kennebel" <jac### [at] kennebelcom> wrote:
> > > ... Is there a 3.7 command line switch/parameter
> > > ...
> Thanks for the response. No matter what I try with the settings suggested there,
> nothing ever seems to change during my renders. So sad. Makes building
> supporting apps challenging. :)

have not used all of them (never needed to) but use '-gr' and '-gs', for
instance, routinely.  have you tried those switches "clean", ie just POV-Ray?
if, as I assume, they work, then the problem would seem to be in the VS code
interface or code.


regards, jr.


Post a reply to this message

From: Tor Olav Kristensen
Subject: Re: VSCode Extension - Render Error Output
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

From: Mr
Subject: Re: VSCode Extension - Render Error Output
Date: 11 Mar 2022 15:40:00
Message: <web.622bb2e08de14cd834c7846e6830a892@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?

You can also have a look at the Blender POV addon which does pipe everything to
console, and even copies it inside the Blender interactive python console, when
one is open.


Post a reply to this message

From: Mr
Subject: Re: VSCode Extension - Render Error Output
Date: 11 Mar 2022 15:55:00
Message: <web.622bb69c8de14cd834c7846e6830a892@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?

Thanks a lot for reviving the extension, but now that I made the switch I
noticed the pov binary path field and gave its path, so expected one step less
to make it work just by clicking the pov icon after that but no, I just got the
info message of the attached capture showing all provided settings. So are we
expected to create a build task by hand in a json file ?


Post a reply to this message


Attachments:
Download '' (161 KB)

Preview of image ''


 

From: kennebel
Subject: Re: VSCode Extension - Render Error Output
Date: 11 Mar 2022 18:55:00
Message: <web.622be10f8de14cd8ace99571a96b55c3@news.povray.org>
"Mr" <m******r******at_hotmail_dot_fr> wrote:
> Thanks a lot for reviving the extension, but now that I made the switch I
> noticed the pov binary path field and gave its path, so expected one step less
> to make it work just by clicking the pov icon after that but no, I just got the
> info message of the attached capture showing all provided settings. So are we
> expected to create a build task by hand in a json file ?

Woohoo! My first bug report for this project! I don't have a modern mac, so
couldn't test. (also, i wasn't even sure anyone would install/use it, thinking i
was stealing from the previous author) Now that I know someone is, I'll have to
see if i get get that mac mini that is sitting in a box running again.

In the meantime, please feel free to email me (jac### [at] kennebelcom), and we can
sort out what I missed on the Mac side, try some fixes, and get it working again
for you/mac users too!


Thanks everyone for the encouragement, i'll keep poking at the switches to get
the output. I'm sure it will work, just need to sit down and really look at it.
:) I really want to make this extension useful again, and learn a few things
along the way.


Post a reply to this message

From: Tor Olav Kristensen
Subject: Re: VSCode Extension - Render Error Output
Date: 11 Mar 2022 19:50:00
Message: <web.622bec408de14cd8afe6ae3e89db30a9@news.povray.org>
"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://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

I know almost nothing about VS Code, but I have a suspicion that Yong Wang's
answer here is relevant:

https://stackoverflow.com/questions/43007267/how-to-run-a-system-command-from-vscode-extension

It seems to me that his code is dealing with what the executed shell command
outputs to stdout or (and ?) stderr.

--
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.