LSP-Forge v0.2.2

LSP-Forge 0.2.2

• Define compiler options as dotted keys in initialization_options so users can override each option while preserving the other defaults.
• Update the README with individual override examples and migration instructions.

Move overrides from settings.forge or initialization_options.forge to forge.path, forge.includePaths, forge.forgeRoot and forge.libDir inside initialization_options, then remove the nested forge object. Restart the server after changing these options.

Changes in 0.2.1

• Put compiler options directly in initialization_options.forge, supported by both Forge servers, and remove the settings-copy hook.
• Delegate registration and unregistration directly to Sublime LSP without tracking global state.
• Place the settings menu under Preferences > Package Settings > LSP > Servers > LSP-Forge.

Move any compiler overrides from settings.forge to initialization_options.forge and remove the old settings overrides. Restart the server after changing initialization options.

Changes from 0.1.0

• Migrate to Sublime LSP's LspPlugin API and automatic settings loading.
• Move syntax, snippets, comment settings and build commands to the independent Forge package.
• Correct the Preferences command caption.

Install Forge and LSP separately. Project LSP client keys previously named forge must become LSP-Forge. The server is still installed manually.

LSP-Forge v0.2.1

LSP-Forge 0.2.1

• Put compiler options directly in initialization_options.forge, supported by both Forge servers, and remove the settings-copy hook.
• Delegate registration and unregistration directly to Sublime LSP without tracking global state.
• Place the settings menu under Preferences > Package Settings > LSP > Servers > LSP-Forge.

Move any compiler overrides from settings.forge to initialization_options.forge and remove the old settings overrides. Restart the server after changing initialization options.

Changes from 0.1.0

• Migrate to Sublime LSP's LspPlugin API and automatic settings loading.
• Move syntax, snippets, comment settings and build commands to the independent Forge package.
• Correct the Preferences command caption.

Install Forge and LSP separately. Project LSP client keys previously named forge must become LSP-Forge. The server is still installed manually.

LSP-Forge v0.2.0

LSP-Forge 0.2.0

• Migrate to Sublime LSP's LspPlugin API and automatic settings loading.
• Move syntax, snippets, comment settings and build commands to the independent Forge package.
• Correct the Preferences command caption.

Install Forge and LSP separately. Project LSP client keys previously named forge must become LSP-Forge; server-specific settings.forge and initialization_options.forge remain unchanged. The server is still installed manually.

LSP-Forge v0.1.0

Forge support for Sublime Text 4:

• .fg syntax highlighting, comment toggling, snippets and build commands.
• Forge language-server integration through the Sublime LSP package.
• Diagnostics, completion, hover and document symbols from the installed Forge server.
• Apache License 2.0; no automatic server downloads or project code execution.

Install LSP-Forge.sublime-package in Sublime Text's Installed Packages folder.
For language-server features, install the LSP package and put forge-lsp on PATH,
or configure an absolute server command in Preferences: LSP-Forge Settings.
See the repository README for setup and the Package Control repository URL.