Changes: (#134)

* Allow viewing of variables with the - character in the name.
* Hover on child variables.
* Display debug on vscode terminal.
* Set XTERM variable to the correct display during debugging with the GDB
  tty option.
* Using gdbtty on WSL and SSH (Windows -> Linux).
* stepOver in subroutines called by PERFORM statement.
* stepInto/stepOut in subroutines called by PERFORM statement.
* Gdbtty running with Ctrl-F5.
* Support for symbolic link directories on linux.

.vscode/launch.json

@@ -19,14 +19,13 @@
 		},
 		{
 			"name": "Tests",
-			"type": "node",
+			"type": "extensionHost",
 			"request": "launch",
-			"cwd": "${workspaceFolder}",
-			"program": "${workspaceFolder}/node_modules/mocha/bin/_mocha",
+			"runtimeExecutable": "${execPath}",
 			"args": [
-				"-u", "tdd",
-				"--colors",
-				"./out/test/"
+				"--disable-extensions",
+				"--extensionDevelopmentPath=${workspaceFolder}",
+        		"--extensionTestsPath=${workspaceFolder}/out/test/suite/index"
 			],
 			"outFiles": [
 				"${workspaceRoot}/out/**/*.js"

README.md

@@ -187,11 +187,22 @@ How to install xterm on Ubuntu:
 ```
 sudo apt-get install xterm
 ```
-You need to call VS Code or VSCodium from the terminal, like this:
-```
-cd  cob_project
-code .
+
+On Linux you can see the output of the application in Vs Code itself. Add `gdbtty` property with `vscode` value to your `launch.json`. Here is an example:
+```json
+{
+            "name": "COBOL debugger",
+            "type": "gdb",
+            "request": "launch",
+            "cobcargs": [
+                "-free",
+                "-x"
+            ],
+            "coverage": false,
+            "gdbtty": "vscode"
+}
 ```
+![GdbTTY](gdbttyvscode.png)
 
 ### Roadmap
 - Mac