Bug: solve(), nsolve() and fsolve() depend on angle mode?

[Tugdual]

Two comments:
- variable definitions are x in CAS and X in Home (even if you tell on which variable you solve, I know this is weird)
- most of the solve functions require an expression with '=' sign. In the best case you'll get a warning telling you that it assumes "=0" otherwise you just don't know what happens

Now, I played with your example and didn't find a connection with use of degrees/radians but the solve functions are extremely chaotic for sure and the help quite inexistant.