@anton_dys  I can use 1D, but it is for the reason you just mentioned that I prefer 2D. It is significantly more readable. I believe the general preference for 1D has something to do with both its reliability and its necessity in standard programming (for example, in Java, C/C++, and any other language you choose, as well as its general use in things like MATLAB and Mathematica). But 2D is nice for, as you mentioned, readability. Though I have noticed that Maple input still appears as 2D, but only in document mode. In worksheets, it appears as 1D, I believe.

And @J Rod: I believe they are working on a patch (based on another thread: http://www.mapleprimes.com/questions/211532-Bugs-In-Parsing). I have no idea when it will be out, though.

@Christopher2222 I am using Windows 10. I've been able to recreate it in every one I do. I have noticed that it does not become a problem (usually - at least with the limited experimenting I did) in Maple input and 1D input, but only in 2D input.

@Christopher2222 I hadn't noticed that. I checked it out in my copy, and lo and behold, there it is (the unusual copy). It explains the unusual comment about encountering a semicolon in the error message, but I'm not sure how it got there, as its appearance is inconsistant. Sometimes it shows up, sometimes not. It seems that Maple is trying to process it, but it is reading the input wrong, as when it is copied I suspect we are seeing what Maple sees (what it parses). By this reasoning, it appears that the 2D math parser is not parsing correctly, for whatever reason - a "feature" of this version, it appears, as it worked just fine in previous ones (apparently including 2016.0, from the sounds of it). The same error is applying to its parsing of x^2 as what you found. Another thing I found is that when it gives the "cannot figure out plotting variable" issue when trying to plot x^2, if I write "plot(x^2,x^2=0..2)" it works (plotting a straight line, of course). To see why, I put it in text pad (like what you did), and found this:

When plot(x^2,x=0..2) works: "plot(x^(2),x=0..2)" is copied to the text pad

When plot(x^2,x=0..2) does not work: "int(`#msup(mi("x"),mn("2"))`, x = 0 .. 2)" is copied to the text pad.

Now, why it does this (why the parser does this)...there in lies the mystery. It seems to be an issue with 2D input....

@Christopher2222  Just scanned the file to see. It came up clean.

I have found that Maple 2016.1 works fine until some point. Once the errors begin, then it stops working. But until that point, it works fine (which, apparently, isn't that long...).

This is extremely unusual.

@Christopher2222 I just tried again. For a little bit, the commands were working, then, out of the blue, they stopped.

Download inconsistent.mw

The commands used for plot: plot(x^2,x=0..2), plot([x,x^2],x=-2..2),plot([x^2,x],x=-2..2), and plot(x^2,x=0..2). The final one gave this error: "Warning, expecting only range variable x in expression `#msup(mi("x"),mn("2"))` to be plotted but found name `#msup(mi("x"),mn("2"))`" This is the same kind of error as the bad syntax error we were talking about (the commands and that error only actually appear in the worksheet itself - not in the inserted contents - if you were to download it).

Any ideas?

@anton_dys Mine is 64-bit (answering Christopher2222), so that would explain the issue I'm having (based on your reply), and I've certainly seen the issues that come up in that link - the error message in particular.

@ I just got Maple 2016 today, and by this point 2016.1 was the version I received.

@Christopher2222 I know the proper syntax. The same commands work in Maple 18, with no changes whatsoever. I believe there is an error within the parser itself. The Error, incorrect syntax in parse: `;` unexpected (near 4th character of parsed string) kind of bug has been confirmed to exist (see this link: http://www.mapleprimes.com/questions/211532-Bugs-In-Parsing).  So, the error is not with how I've entered it.

Edit: I deleted two equations that give the pink error messages, but the equations show back up in the error messages. I just forgot to delete the error messages from the document.