Switch branches/tags
Nothing to show
Find file History
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
vscode [vscode] Update dev dependencies vscode, vsce Nov 28, 2018
README.md Mention the Emacs client in the documentation Nov 29, 2018

README.md

Editor Integration

This document contains information about how to configure an editor to use SourceKit-LSP. If your editor is not listed below, but it supports the Language Server Protocol (LSP), see Other Editors.

Visual Studio Code

To use SourceKit-LSP with Visual Studio Code, you will need the SourceKit-LSP Visual Studio Code extension. Documentation for Building and Installing is in the extension's README. There is also information about Configuration. The most common settings are listed below.

After installing the extension, settings for SourceKit-LSP can be found in Preferences > Settings under Extensions > SourceKit-LSP or by searching for the setting prefix sourcekit-lsp..

  • sourcekit-lsp.serverPath: The path to sourcekit-lsp executable
  • sourcekit-lsp.toolchainPath: The path to the swift toolchain (sets SOURCEKIT_TOOLCHAIN_PATH)
  • sourcekit-lsp.tracing.server: Traces the communication between VS Code and the SourceKit-LSP language server

Sublime Text

Before using SourceKit-LSP with Sublime Text, you will need to install the LSP package from Package Control. To configure SourceKit-LSP, open the LSP package's settings. The following snippet should be enough to get started with Swift.

You will need the path to the sourcekit-lsp executable and the Swift toolchain for the "command" and "env" sections.

{
  "clients":
  {
    "SourceKit-LSP":
    {
      "enabled": true,
      "command": [
        "<path to sourcekit-lsp>"
      ],
      "env": {
        "SOURCEKIT_TOOLCHAIN_PATH": "<path to toolchain>",
      },
      "languages": [
        {
          "scopes": ["source.swift"],
          "syntaxes": [
            "Packages/Swift/Syntaxes/Swift.tmLanguage",
          ],
          "languageId": "swift"
        },
        {
          "scopes": ["source.c"],
          "syntaxes": ["Packages/C++/C.sublime-syntax"],
          "languageId": "c"
        },
        {
          "scopes": ["source.c++"],
          "syntaxes": ["Packages/C++/C++.sublime-syntax"],
          "languageId": "cpp"
        },
        {
          "scopes": ["source.objc"],
          "syntaxes": ["Packages/Objective-C/Objective-C.sublime-syntax"],
          "languageId": "objective-c"
        },
        {
          "scopes": ["source.objc++"],
          "syntaxes": ["Packages/Objective-C/Objective-C++.sublime-syntax"],
          "languageId": "objective-cpp"
        },
      ]
    }
  }
}

Emacs

There is an Emacs client for SourceKit-LSP in the main Emacs LSP repository.

Other Editors

SourceKit-LSP should work with any editor that supports the Language Server Protocol (LSP). Each editor has its own mechanism for configuring an LSP server, so consult your editor's documentation for the specifics. In general, you can configure your editor to use SourceKit-LSP for Swift, C, C++, Objective-C and Objective-C++ files; the editor will need to be configured to find the sourcekit-lsp executable (see the top-level README for build instructions), which expects to communicate with the editor over stdin and stdout.