I need some help here. I think Visual Studio Code is a great replacement for PowerShell ISE, however, there a few things that I am not sure if I am doing something wrong or if VS Code is just buggy yet. When debugging my PowerShell code, not only Intellisense does not work (I press the up/down button and nothing happens - Using the latest VS Code available and the latest PS Extension) and for a a very strange reason when I set a global variable in my code VS Code creates it as a Local variable instead.
Here is what I get in VS_Code:
And here is what I get in PS_ISE:
Because of that, obviously my code crashes because as soon as I change the scope the variables are no longer available.
This is really preventing me from fully using VS Code completely (it forces me to debug code using PS ISE). If I'm doing anything wrong, any help is greatly appreciated.
Related
I have SWI-Prolog 8.2.4 installed, and I was trying to get it to work in Visual Studio Code with the extension "VSC-Prolog" made by Arthurwang.
If I try to run a program, everything works correctly, however I realized that I cannot use the gtrace tool, because when I try to do it, a strange message appears on the console asking me if I was not wrong and I wanted to write "trace" (which is something different than what I'm looking for).
What I tried later is to write gtrace in the console but outside of Visual Studio Code to see if there I could make use of that tool. However, the same problem appears:
However, if I open swi-prolog's default text editor (swipl-win.exe), gtrace works fine there.
Why could this be happening, and how could I fix it?
Hope I can use prolog correctly in Visual Studio Code.
I'm having a problem with Rust that I strongly suspect has do with a disconnect between Cargo and VS Code.
I build my Cargo project with cargo new project
I edit my src/main.rs with VS Code and save it.
I issue cargo run
I see the result from the hello world main.rs instead of the results of the changes I made.
What I find interesting is that if I do a cat src/main.rs from the terminal, I see the original Rust code, even though VS Code assures me that it saved it and shows me that code even if I restart VS Code.
I've had this problem on a couple of computers now (same OS, Fedora 28). I strongly suspect that Cargo is doing some buffering somewhere that is defeating VS Code. Has anyone else seen this behavior or know the cause? Are there any cures or work-arounds?
#Tau turned out to be correct. Using Kwrite, the changes seemed to propagate correctly. What's really odd is that Kwrite and VS Code seemed to synchronize with one another. That's really annoying for me as I am a VS Code fanatic. Maybe I post an issue about this for VS Code. Thanks to all for their suggestions.
Make sure autosave is enabled in VSCode.
I've been working on some scripts for Windows using Visual Studio Code and was surprised that when I type WScript on a line the IntelliSense pops up the correct code completion information, even on my Mac.
I've read the documentation on the VSC website and suspect its either coming out of the built-in JavaScript support or Automatic Type Acquisition from some included library but really would like to find out exactly where this is coming from. So far either my Google-Fu is or nobody has written a thing about it because I can't find any information anywhere. Can anyone answer this one?
It's built into TypeScript. In VSCode, it's actually easy to find the source because you can press F12 on the definition in code, and it will show you the .d.ts:
When I first started using Visual Studio Code for my cobol, it was working fine. But lately when I try to compile my code after saving it in vsc it gives errors about there being weird characters.
If I do the same changes in Notepad++ it works fine. I've been going through the settings in vsc but I cannot find anything wrong in there. But then again I don't know that much about it. I'm also using the extension cobol syntax support from bitlang.
Does anybody know how this is possible? Is there some setting that messes this up? I cannot really show any screens or anything. since this is all work related and I'm not allowed to share.
My guess is, that this is related to the code page used to save the project.
Notepad++ by default uses UTF-8. you may need to change the code page on Visual Studio Code to UTF-8.
https://code.visualstudio.com/docs/getstarted/settings
I'm coming from a pure Windows Visual Studio programming background with little Linux experience. It seems possible to use VS Code to program in Julia, but I can't figure out how to get things set up correctly.
Does anybody have good example launch.json, tasks.json, or other files that can serve as an example to build from?
This would be a great thing to see in a detailed tutorial.
Here is how things work if you are using the Julia extension for VisualStudio Code.
The extension adds a bunch of new commands. They all start with "julia", so filtering by that string should show you everything you can do with the extension.
In terms of running Julia code, the extension offers only two options right now. First, you can execute a command to start a REPL. This will just show a default Julia prompt, and you can interact with it like you would with any other Julia REPL. The second is that there is also a command, triggered by Ctrl + Enter, to send either the current editor selection or the current editor line to this REPL.
There is currently no further integration offered by the Julia extension. We do plan to add debugger support in the future, at which point I would expect F5 to start the current file in the debugger, or something like that. But that functionality is probably a couple of months away.