Roger. 

On Wed, Apr 13, 2022 at 08:28:25AM +0100, Roger Whiteley via Discuss wrote: > The use or include looks like [doesn't matter which]. > > use <../g1-dot-5/testfilename.scad> > > I've got this horrible feeling that the dash in front of the number 5 is > being interpreted as a subtract, because the number 5 is maroon, so the use > or include fails. I would think that the syntax highlighting in the editor is independent of the interpretation of the program. Works-for-me, but i'm using 2019.5 ... My test included. Roger. -- ** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 ** ** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 ** f equals m times a. When your f is steady, and your m is going down your a is going up. -- Chris Hadfield about flying up the space shuttle.

On 13.04.22 09:34, Rogier Wolff wrote: > On Wed, Apr 13, 2022 at 08:28:25AM +0100, Roger Whiteley via Discuss wrote: >> The use or include looks like [doesn't matter which]. >> >> use <../g1-dot-5/testfilename.scad> >> >> I've got this horrible feeling that the dash in front of the number 5 is >> being interpreted as a subtract, because the number 5 is maroon, so the use >> or include fails. > I would think that the syntax highlighting in the editor is > independent of the interpretation of the program. Yes, the syntax highlighting in the editor is independent of the lexter used to interpreter scad code. I just recently worked on getting the two closer to each other. Recent Nightly Builds of openscad should do a better job of correctly highlighting use and include. One clear example to show the syntax highlighting is/was bugged: use </* > echo("Test"); Parsing design (AST generation)... WARNING: Can't open library '/* '. Compiling design (CSG Tree generation)... ECHO: "Test" Compiling design (CSG Products generation)... Anything but the most recent builds highlight as if /* starts a comment - which it does not. The main lexter is in a specific sub state after find use < and only leaves it after finding >. The syntax highlighting lexter (until recently) did not replicate that. The syntax highlighting of the nightly build now shows the example above correctly. With kind regards, Michael Frey