Steel language server

Installation

From the directory of this crate, run:

cargo install --path .

This will install the steel-language-server to your path.

Configuration in helix can be done by adding the following to your languages.toml file:

[[language]]
name = "scheme"
language-servers = [ "steel-language-server" ]

[language-server.steel-language-server]
command = "steel-language-server"
args = []

Configuration in neovim can be done by adding the following to your configuration

configs.steel = {
    default_config = {
        cmd = { "steel-language-server" },
        filetypes = { "scheme" },
        root_dir = function(_)
            -- We can run on single file, so root dir doesn't really matter.
            require("lspconfig.util").root_pattern "*"
        end,
        single_file_support = true,
        docs = {
            description = [[
Steel language server.

Install from: https://github.com/mattwparas/steel/tree/master/crates/steel-language-server

Check the repo for more configuration.
]],
            default_config = {}
        }
    }
}

Now you can call

require'lspconfig'.steel.setup {
  -- Your usual configuration (handlers, capabilities, etc.) goes here.
}

VSCode, and emacs installation instructions coming soon.

Configuration

If you're embedding steel within a host application, it is possible the language server does not have knowledge of the globals given by the host application. To make these available to the language server, create a configuration file for the language server under the path specified by the env var STEEL_LSP_HOME.

For example, I have set my STEEL_LSP_HOME to ~/.config/steel-lsp/ and added the file globals.scm:

(define keymaps (#%module "helix/core/keymaps"))

(define (register-values module values)
  (map (lambda (ident) (#%module-add module (symbol->string ident) void)) values))

(register-values keymaps
                 '(helix-current-keymap *buffer-or-extension-keybindings*
                                        *reverse-buffer-map*
                                        helix-merge-keybindings
                                        helix-string->keymap
                                        *global-keybinding-map*
                                        helix-deep-copy-keymap))

(define typable-commands (#%module "helix/core/typable"))
(define static-commands (#%module "helix/core/static"))
(define editor (#%module "helix/core/editor"))

(register-values typable-commands '())

(#%ignore-unused-identifier "_")

keymaps

The following rules apply: Any global value that is defined as a builtin module, will be interpreted by the LSP and used, or evaluated as a top level env var. So either defining keymaps or evaluating like so on the last line of the example will get the module to show up.

Any symbol added with #%ignore-unused-identifier will escape that symbol from being shown as an unused identifier.

Any global registered with #%register-global will be ignored as a free identifier as well.