VSCode = Visual Studio Code (Editor ++) with QB64 extension

[SMcNeill]

@grymmjack thanks for soul bearing reply. Doing those vid's for yourself firstly sure explains allot. My dad passed from Alzhiemers/Parkensons 2014 and going through same now with mom at 92, she does crossword puzzles to help keep mind fit but nothing sticks in short term memory, hard to get use to... 

Anyway so glad you got back to us here!

One question inquiring minds must know:
"What is Lint or Linting? Never heard of it."

It is interesting to see a professional doing stuff on his computer, kind of mind blowing.

Every new tech thing comes with a manual that is a little book that could takes hours to go through, then there is the Quick Start page/diagram that gets you up and running in 5-10 minutes. 

I would like the Quick Start thing to get the QB64 Extension you are working with loaded into VSCode so I can start editing a QB64 program, connecting with my QB64 files and exploring the bells and whistles of VSCode and QB64 Extension from there.

1. Step 1: You have to have VsCode. 

1. Step 2: This file. (I think.) https://github.com/QB64Official/vscode/r...0.8.7.vsix 

1. Step 3: Should be able to start VS Code and install from within the VS Extension Manager (Tools->Extension Manger)

[bplus]

OK it's in. Funny I tried that very file before and no luck,
   

Now I have to tell it where QB64 is, where?

Update: found it

[bplus]

Under Extensions here
   

But I had to copy QB64pe.exe rename it QB64.exe in another Folder and then paste that exe back into QB64pe Folder and I could finally run some code.

BTW Thankyou Steve, your Quick Guide had me trying again.

Oh yeah, I also had to fill a space in Folder name with a - hyphen.

[SMcNeill]

I think you can put it in single quotes or quotes if it has a space, a lot like SHELL commands.  

[grymmjack]

@grymmjack thanks for soul bearing reply. Doing those vid's for yourself firstly sure explains allot. My dad passed from Alzhiemers/Parkensons 2014 and going through same now with mom at 92, she does crossword puzzles to help keep mind fit but nothing sticks in short term memory, hard to get use to... 

Anyway so glad you got back to us here!

One question inquiring minds must know:
"What is Lint or Linting? Never heard of it."

It is interesting to see a professional doing stuff on his computer, kind of mind blowing.

Every new tech thing comes with a manual that is a little book that could takes hours to go through, then there is the Quick Start page/diagram that gets you up and running in 5-10 minutes. 

I would like the Quick Start thing to get the QB64 Extension you are working with loaded into VSCode so I can start editing a QB64 program, connecting with my QB64 files and exploring the bells and whistles of VSCode and QB64 Extension from there.

Hey @bplus you are welcome.

Lint and Linting is simply the process of checking syntax for validity. This happens every line in QB64 IDE. You get the errors at the bottom when linting fails. The "linting" is the common term that other languages use too.

Check this link on Wikipedia for more information.

OK got you, I will help you with that, video will come in a bit!

Glad to help!

[grymmjack]

@smcneill Exactly! You guys got it.

Yep, you have to copy the qb64pe.exe to qb64.exe right now - but @durus is working on a change that let's us specify the actual compiler file itself in the latest development branch for qb64 vscode extension - but yeah, recommend you just stick with this latest one you installed, and you can freely change the \ back slashes to forward slashes / and powershell might be ok for you. Otherwise, set your default terminal to CMD.

CTRL+SHIFT+P, type "terminal default", choose CMD.exe from the list, with arrow keys, then hit ENTER.

Hope that helps!

[mnrvovrfc]

Somebody is complaining about the question mark automagically not becoming "PRINT" (facepalm)

Also remember that BASIC, like Pascal, is a programming language that disregards letter case. Not like Python where "Number" and "number" could be two different variables.

Might need an option apart from "How keywords are formatted" related to names of variables and subprograms.

There are other subtleties such as single-line "IF... THEN" against "IF... THEN... ELSEIF... ELSE... ENDIF", this could be hard to get right. For example, Kate always boldfaces the two letters that come right after "THEN" if anything follows "THEN". It's a strange quirk.

Good work on the VSCode template but that program is something I'm not interested in. (thumbs up)