# VS Code extension updates, Pascal LSP updates (for VS Code and other editors)

**URL:** <https://forum.castle-engine.io/t/vs-code-extension-updates-pascal-lsp-updates-for-vs-code-and-other-editors/1423>\
**Category:** News\
**Created:** [November 9, 2024, 8:17am UTC](https://forum.castle-engine.io/t/vs-code-extension-updates-pascal-lsp-updates-for-vs-code-and-other-editors/1423 "2024-11-09T08:17:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![michalis](https://forum.castle-engine.io/user_avatar/forum.castle-engine.io/michalis/32/3_2.png) [@michalis](https://forum.castle-engine.io/u/michalis)\
**Post date:** [November 9, 2024, 8:17am UTC](https://forum.castle-engine.io/t/vs-code-extension-updates-pascal-lsp-updates-for-vs-code-and-other-editors/1423/1 "2024-11-09T08:17:50Z")

</div>

| [![VS Code code completion](https://forum.castle-engine.io/uploads/default/original/2X/d/d2a735375d279812246c74765c99adb847fe80a4.png)](https://castle-engine.io/wp/wp-content/uploads/2024/03/vscode_ext_1.png "VS Code code completion") |
| [![VS Code symbols in file](https://forum.castle-engine.io/uploads/default/original/2X/3/3223b8a531ea47775cbc7766a6822cae0f1397ba.png)](https://castle-engine.io/wp/wp-content/uploads/2024/03/vscode_ext_3.png "VS Code symbols in file") |
| [![VS Code symbols in workspace](https://forum.castle-engine.io/uploads/default/original/2X/9/9f3415fef4ffea510adcb553e648c520cf04cc71.png)](https://castle-engine.io/wp/wp-content/uploads/2024/03/vscode_ext_2.png "VS Code symbols in workspace") |
| [![VS Code running Castle Game Engine task](https://forum.castle-engine.io/uploads/default/original/2X/6/66b27ed8aadef129dc0d6b62795fae7b00571593.png)](https://castle-engine.io/wp/wp-content/uploads/2023/04/Zrzut-ekranu-z-2023-04-29-02-11-53.png "VS Code running Castle Game Engine task") |

Recently we did some updates to our [VS Code extension for Castle Game Engine](https://castle-engine.io/vscode) and the _Pascal LSP_.

1. _VS Code extension_ now uses the FPC path you set for more things. Namely, the build tool (which is executed when you press _“Compile”_ from VS Code) will reliably use this FPC. This means that there’s no need to have FPC on `$PATH` anymore to use CGE from VS Code. Just configure FPC location in VS Code and everything should “just work”.

Further notes:

  - Direct link to [the extension in the marketplace](https://marketplace.visualstudio.com/items?itemName=castle-engine-team.castle-engine).

  - We actively develop our VS Code extension, see the [changelog](https://marketplace.visualstudio.com/items/castle-engine-team.castle-engine/changelog) for all details. I (Michalis) use it during all my work on the engine nowadays, so I really need it to be good and handle code in various stages of “in progress” 🙂

  - Reminder: The extension is useful for development of any Pascal projects, whether using _Castle Game Engine_ or not. Pascal syntax highlighting and code completion (provided by LSP) work regardless of the _Castle Game Engine_. Only the _“Compile”_, _“Run”_ features rely on CGE project ([CastleEngineManifest.xml](https://castle-engine.io/project_manifest)).

2. Our Pascal LSP (`pasls` binary present in [engine downloads](https://castle-engine.io/download)) also got updates. It now better reports errors, capturing all possible Pascal parsing errors and returning useful error messages for them — with filename, line and column number. The idea is that, when working, you naturally sometimes have a code that isn’t (yet!) correct, so the code tools sometimes cannot provide their services (completing, jumping to definition etc.). In such case it’s important that you get useful errors, _why_ is your current code wrong.

---

<div class="post-metadata">

**Author:** ![michalis](https://forum.castle-engine.io/user_avatar/forum.castle-engine.io/michalis/32/3_2.png) [@michalis](https://forum.castle-engine.io/u/michalis)\
**Post date:** [December 28, 2024, 1:37pm UTC](https://forum.castle-engine.io/t/vs-code-extension-updates-pascal-lsp-updates-for-vs-code-and-other-editors/1423/2 "2024-12-28T13:37:57Z")

</div>

Listed on December 28, 2024, 1:37pm UTC