extemporelang / vscode-extempore Goto Github PK

not such a big issue on macos/linux (since install puts it on your path) but it needs to be there on Windows

When I use the CTRL+Shift+P -> Extempore Download Binary function, it returns a 404 error

More then half of the expression in examples\core\covers.xtm (for example) no longer evaluate (don't find expr correctly)

Right-clicking and selecting Format Selection on a block of code usually removes the last line. The workaround is selecting an extra empty line below the block.

Formatting the entire document at once also removes the last line.

Currently when the user evals a code function there is very minimal feedback. It should be very obvious to the user that it has been successful.

One suggestion would be to briefly highlight the block that has been evaluated.

Similarly to #1, when evaling code it'd be very nice if the value sent back by the server gets printed out on screen briefly eg in the status bar.

For example evaluating (random 10 20) would result in a number eg 15 printed out in the status bar.

Is this possible at all in VSCode?

openingBracketPos will quite happily match against opening brackets inside strings and comments - which then causes problems downstream.

EXAMPLE:
Try to evaluate the first println after the comment evaluates (i.e. matches) from the "(" down to "BYE)"

;; test example
(println "(" (* 6 7))

(println "BYE)")

VSCode should have the equivalent of C-c C-z in Emacs. That is it should be possible to start Extempore without having to mess around in the console. By default extempore should be started in the same folder as the currently active file.

Currently there is no easy way to access the doc-strings. The plugin should support it in two ways:

1. tooltips - Tooltips should use the docstring for functions.
2. shortcut - There should be a way to show the help in the panels below/to the side of the editor.

Probably the easiest way to do this is just to submit pull requests to:

• https://github.com/shaunlebron/vscode-parinfer
  and
• https://github.com/clptn/code-paredit

and get Extempore added as a language mode for them. However maybe there's a more elegant way to achieve this?

macOS 10.13.3 High Sierra
VSCode Insiders 1.21.0
I've just downloaded and installed from the binary. I've gotten as far being able to issue the extempore start command whereupon I get the following showing in my terminal window:

I notice that it shows an error message namely Error binding extempore address to socket.

More in hope rather than judgement, I press on and issue the extempore connect whereupon I am prompted to accept the default entry of localhost and the port 7099. There is no indication of success or failure here.

Finally, I position the cursor on the same line as the (println "Hello, World!") code and press Cmd-Enter. I see the brief orange highlight, but there is no other indication, especially in the Debug Console that the program has produced any output. In view of the earlier error message, it does seem unlikely that it has worked.

I'm sure it's something simple to fix, but what that could be, I haven't a clue. Help!!

One really nice thing that SuperCollider IDE has is really tight integration with helpfiles. At a minimum it should be possible to view and navigate the documentation from within the plugin.

VSCode Version: 1.30.2
OS Version: 10.14.1

With .xtm files and the extension loaded I can't copy/paste text. Or better, the text is copied and pasted for a fraction of a second but then it disappears.

Anyone else had the same issue?

Possibly related discussions here:

• microsoft/vscode#24112

... although in my case this happens only with .xtm files (irrespectively of whether I start vscode from the terminal or finder).

VSCode Version: 1.30.2
OS Version: 10.14.1

With .xtm files and the extension loaded I can't copy/paste text. Or better, the text is copied and pasted for a fraction of a second but then it disappears.

Anyone else had the same issue?

Possibly related discussions here:

• microsoft/vscode#24112

... although in my case this happens only with .xtm files (irrespectively of whether I start vscode from the terminal or finder).

we should have some tests, particularly for the s-expression parsing stuff

https://code.visualstudio.com/docs/extensions/testing-extensions