All Projects → klaaspieter → coc-sourcekit

klaaspieter / coc-sourcekit

Licence: MIT license
Swift language server extension using sourcekit-lsp for coc.nvim.

Programming Languages

javascript
184084 projects - #8 most used programming language
typescript
32286 projects
shell
77523 projects

Projects that are alternatives of or similar to coc-sourcekit

coc-discord-rpc
😎 An awesome and fully customizable coc-extension to get Discord Rich Presence integration with NeoVim.
Stars: ✭ 139 (+127.87%)
Mutual labels:  coc
Bridgecraft
Generate Swift interface for ObjC bridging headers
Stars: ✭ 62 (+1.64%)
Mutual labels:  sourcekit
async-clj-omni
Async Clojure Completion for various (n)vim completion engines
Stars: ✭ 51 (-16.39%)
Mutual labels:  coc
coc-toml
Toml extension for coc-nvim, using taplo for lsp engine
Stars: ✭ 52 (-14.75%)
Mutual labels:  coc
coc-webview
Using an external browser to support the webview in coc.nvim.
Stars: ✭ 21 (-65.57%)
Mutual labels:  coc
vim-setup
👾 My NeoVim configuration for Scala & Haskell development (permanently moved to https://github.com/gvolpe/dotfiles)
Stars: ✭ 31 (-49.18%)
Mutual labels:  coc
coc-sql
SQL extension for coc.nvim
Stars: ✭ 104 (+70.49%)
Mutual labels:  coc
emacs-sourcekit-lsp
Emacs LSP client for SourceKit-LSP (https://github.com/apple/sourcekit-lsp), a Swift/Objective-C/C++ language server created by Apple
Stars: ✭ 25 (-59.02%)
Mutual labels:  sourcekit
coc-elixir
Elixir language server extension based on elixir-ls for coc.nvim
Stars: ✭ 150 (+145.9%)
Mutual labels:  coc
code-of-conduct
Internal documentation of the DSF Code of Conduct committee
Stars: ✭ 30 (-50.82%)
Mutual labels:  coc
pycon-code-of-conduct
PyCon Korea's code of conduct
Stars: ✭ 24 (-60.66%)
Mutual labels:  coc
code-of-conduct
The rule of St. Benedict as your Code of Conduct
Stars: ✭ 21 (-65.57%)
Mutual labels:  coc
coc-stylelint
Stylelint language server extension for coc.nvim
Stars: ✭ 42 (-31.15%)
Mutual labels:  coc
vim-nayvy
🌑 Enriching python coding in Vim 🐍
Stars: ✭ 66 (+8.2%)
Mutual labels:  coc
coc-volar
Volar (Fast Vue Language Support) extension for coc.nvim
Stars: ✭ 143 (+134.43%)
Mutual labels:  coc
skit
yaml -> sourcekit -> json
Stars: ✭ 29 (-52.46%)
Mutual labels:  sourcekit
coc-neco
viml completion source for coc.nvim
Stars: ✭ 22 (-63.93%)
Mutual labels:  coc
coc-flutter-tools
Rich Flutter development experience for (Neo)vim
Stars: ✭ 51 (-16.39%)
Mutual labels:  coc
quick.nvim
A very fast Lua based Neovim configuration that uses coc.nvim for intellisense
Stars: ✭ 159 (+160.66%)
Mutual labels:  coc
macsimus
A custom editor based on NeoVim and inspired from Vim and Emacs to maximise productivity.
Stars: ✭ 18 (-70.49%)
Mutual labels:  coc

coc-sourcekit

Sourcekit language server extension for coc.

Install

In vim or neovim, run command:

:CocInstall coc-sourcekit

Features

See sourcekit-lsp.

Configuration options

Key Description Default
sourcekit.enable Enable sourcekit extension true
sourcekit.commandPath Path to sourcekit-lsp binary Output of which sourcekit-lsp
sourcekit.trace.server Trace the communication between coc and the sourcekit language server
sourcekit.sdkPath The path to the desired SDK Nothing
sourcekit.sdk The name to the desired SDK to be fetched Nothing
sourcekit.targetArch The name of the target (e.g x86_64-apple-ios13.2-simulator) to generate code
sourcekit.args Extra arguments to pass to the lsp []
sourcekit.env Environment variables to pass to the lsp. {}

Environment Variables

You can configure SourceKit's logging and toolchain path through sourcekit.env:

"sourcekit.env": {
	"SOURCEKIT_TOOLCHAIN_PATH": "/home/USER/swift-DEVELOPMENT-SNAPSHOT-2021-07-30-a-ubuntu20.04/",
	"SOURCEKIT_LOGGING": "3" // verbose logging
}

Development

  1. Run yarn build or yarn build:watch
  2. Run yarn run link:add to link extension
  3. Open a Swift file in vim

To see that it worked use :CocOpenLog.

Alternatively a .env is provided which allows for tailing the logs outside of vim:

# In the split/tab you will open vim
source .env

# In another split/tab
tail -f coc.log

Or source it automatically.

Acknowledgements

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].