Freepascal support for Visual Studio Code

[helio]

Freepascal and Pas2Js support for Visual Studio Code.

 - Project manager
 - Project building
 - Project settings
 - Code Completation
 - Code Definition
 - Code Indentation
 - Code Jump
 - Code Suggestion
 - Code Refactory
 - Code Snippets
 - Syntax Coloring

 https://github.com/heliosroots/fp-vscode

[Thaddy]

Will test. Note ther are a few others, so curious..

[helio]

Create, edit, compile and manage your freepascal and pas2js font codes with VSCode... an alternative to lazarus ide

[PascalDragon]

Regarding code completion and such there is also a Pascal Language Server that makes use of Lazarus' CodeTools package to provide everything. To avoid the hassle to implement support for every language construct yourself.

[helio]

internally I use codetools, so it works as in the lazarus ide...

[PascalDragon]

Ah, hadn't drilled that far down into your code yet.

[PierceNg]

Freepascal and Pas2Js support for Visual Studio Code.

Hi. Other than configuring in settings, what else need to do? I have set up the paths to the fpc and pas2js compilers and their source locations.

When I open a .lpr file (for pas2js) and right click 'go to definition' or 'peek definition', it says not found.

(In the same instance of VS Code, Omni Pascal extension finds the definitions.)

[helio]

- You should always load the configuration file project.lpr.json => F10
- If the code is legacy you must create the file project.lpr.json => CTRL+ALT+N => template settings
- It is important not to use other extensions there may be a conflict between them, if you can disable them

[PierceNg]

- You should always load the configuration file project.lpr.json => F10
- If the code is legacy you must create the file project.lpr.json => CTRL+ALT+N => template settings

I was opening an existing project which has an .lpi file from Lazarus. I created a new project that generated project1.lpr.json, then copied it to myproject.lpr.json. Then reopened VS Code and use F10 to load myproject.lpr.json. Then code browsing works.

So using F10 to load the project JSON file is the key step?

- It is important not to use other extensions there may be a conflict between them, if you can disable them

Yes I was testing them one at a time.

[helio]

- The lazarus Ide, uses the associated ".lpi" file, to maintain the project configuration
- Fp-Vscode, uses the ".lpr.json" files, to keep the project configuration

- Then you should always load the ".lpr.json" file
- It must be manual because you can have multiple ".lpr.json" files
- Upload only once, and use it in all your work

[helio]

- If you already have a ready-made project generated in the lazarus ide, you can use ctrl+alt+n and choose the "settings" template so it will create a configuration file
- Then it's just up to you to adjust these settings and set the dependencies