pencil code issue

Skip to first unread message

Ian Michael

May 16, 2016, 4:54:06 AM5/16/16

Whenever we start pencil code we get the syntax error message and have to “do cs” to remove it. Even if their is no syntax error the message still appears.

Hope you can help.


Ian Michael

Perth Montessori School

David Bau

May 16, 2016, 8:05:02 AM5/16/16
to Ian Michael, pencilcode-development
Hello - can you email a screenshot?


You received this message because you are subscribed to the Google Groups "pencilcode-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
For more options, visit

David Bau

May 16, 2016, 9:23:52 AM5/16/16
to Ian Michael, pencilcode-development
Sounds like it is a problem with the Grammerly together with Safari.

The general issue is that the pencil code console will highlight errors of any sort that occur when a program is run - and unfortunately there are some extensions that cause errors on some browsers!  These errors are normally not noticed when you use the extension, but Pencil Code will see them and report them.

Hopefully it will be possible for you to either use Chrome or disable Grammerly while using Pencil Code?


On Mon, May 16, 2016 at 9:20 AM, Ian Michael <> wrote:
Yep! Thanks David, it was the Grammarly extension that checks the grammar of anything that is written in a dialogue box, so it makes sense. I only had two extensions anyway so it was good. It would seem that Grammarly plays nicer with Chrome than with Safari?



On 16 May 2016, at 9:03 PM, David Bau <> wrote:

Thanks!  The error is coming from the "babel/polyfill" line which is something that Pencil Code does not do.  It might be something that a Safari extension is doing.

Under Safari preferences "Extensions" it should list your extensions - if you disable all of them, does the error go away?

If so, can you tell which extension is causing the issue?


On Mon, May 16, 2016 at 8:56 AM, Ian Michael <> wrote:

I thought that might have been the case. This looks like the real thing.



On 16 May 2016, at 8:42 PM, David Bau <> wrote:

Hi - sorry - for the last step, I meant: go back to the page on which causes the error, and send me a screenshot of _that_ again with the developer console showing.  (You've sent me a screenshot of the developer console showing on apple's page.)


On Mon, May 16, 2016 at 8:36 AM, Ian Michael <> wrote:
This is what I get.


and this is my version of safari. Just tried with Chrome and don’t seem to get the error.


Reply all
Reply to author
0 new messages