Made for Pulsar!

This package was written specifically for Pulsar and did not exist in the Atom package repository.

pulsar-coc

A Pulsar package that reads your coc.nvim coc-settings.json and automatically starts those language servers inside Pulsar — no duplicate configuration needed.

How it works

On activation, pulsar-coc reads ~/.vim/coc-settings.json (configurable) and starts every entry under languageserver as an LSP server in Pulsar. Each server's capabilities (autocomplete, diagnostics, hover, go-to-definition, formatting, etc.) are wired into Pulsar's IDE service layer automatically.

Example

Given this coc-settings.json:

{
  "languageserver": {
    "ruff": {
      "command": "/Users/you/.local/bin/ruff",
      "args": ["server"],
      "filetypes": ["python"],
      "rootPatterns": [".git", "pyproject.toml"],
      "initializationOptions": {
        "settings": { "lineLength": 88, "fixAll": true, "organizeImports": true }
      }
    },
    "ty": {
      "command": "/Users/you/.local/bin/ty",
      "args": ["server"],
      "filetypes": ["python"],
      "rootPatterns": [".git", "pyproject.toml"]
    }
  }
}

Both ruff and ty will be started and their diagnostics, completions, and other capabilities surfaced in Pulsar when you open a Python file.

Requirements

atom-ide-base — IDE UI components (installed automatically)
busy-signal — busy indicator
linter + linter-ui-default — diagnostics UI

Configuration

Setting	Default	Description
`pulsar-coc.cocSettingsPath`	`~/.vim/coc-settings.json`	Path to your coc-settings.json

Supported coc-settings.json fields

Field	Description
`command`	Path to the LSP server binary
`args`	Arguments passed to the binary
`filetypes`	File types the server handles
`initializationOptions`	Passed to the server's `initialize` request

rootPatterns is noted but Pulsar uses the project root automatically.

License

MIT

Services

Dependencies