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
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.
Visual studio code has too many annoying suggestions.
But the real one are not showing at the first time, unless we input enough prefix characters.
Any idea? Wrong settings?
I don't know how to describe my problem except via picture.
Don't judge my code, but if you look between the letters you will see random bits of characters. This Doesn't seem to effect how it compiles and runs, but I really want it to go away.
I've tried restarting visual studio code, closing the document withing visual studio code and reopening, and restarting my computer. Beyond that, I have no ideas. I think this problem may have started when I elected to install C/C++ Intellisense.
a Screenshot of my Code
fyi: I don't know how to word my problem in a way that helps google take me to relevant sources.
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:
I'm trying to set up a simple blog on via Visual Studio and Jekyll but Jekyll can't seem to parse markdown for my posts correctly. Here's the result for my file as is.
Notice that per Visual Studio, this currently is saved with BOM but still builds.
I'm aware that files need to have NO BOM (Byte Order Marker) so I've tried saving it without it but still can't get any results. Anyone have any ideas?
EDIT: Here's backtrace output per comments:
EDIT2: I've tried all the possible line endings available and still can't seem to get anything going. Per #Waylan 's comments I looked into issue #3304 but it seems it isn't fully resolved. Check out this issue if you'd like to add any comments
Seems this was occurring because I was adding via Visual Studio.
You must add the files as a regular text file in Windows Explorer - then you'll be able to edit them in Visual Studio as you like.
Hopefully we'll get support for this in later version of Jekyll or Visual Studio will change whatever it is that's causing the issue. I've made note of the issue with Jekyll already here though if anyone would like to add on to it