Someone here to help me with nixd?

573 · June 12, 2023, 8:41pm

Is there like a complete newbies guide to use nixd (lsp) with nvim already ?

I’m trying to wrap my head around the instructions given at their editor setup page, but I can’t get my editor to do what the gifs suggest it should with any nix file I tried.

I must be missing something important there and I would so much like to be able to turbo-charge my editing with this awesome lsp implementation.

iFreilicht · June 13, 2023, 10:17am

Nixd has been announced five days ago, so I doubt there’s any tutorials on it yet.
Maybe @inclyc can help you directly?

Could you share your nvim setup files and what changes you made in an attempt to enable nixd?

inclyc · June 13, 2023, 3:53pm

Did you write workspace configuration?

github.com

nix-community/nixd/blob/093a4846322813e7cb1c40ace11f5edbe523ef00/docs/user-guide.md#configuration

## User Guide

### Installation

Our flake.nix provides a package named `nixd`, and an overlay to nixpkgs that add the `nixd` package.
So, if you would like to use `nixd` in your flake:

```nix
{
  description = "My configuration";

  inputs = {
    nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
    nixd.url = "github:nix-community/nixd";
  };

  outputs = { nixpkgs, nixd, ... }:
    {
      nixosConfigurations = {
        hostname = nixpkgs.lib.nixosSystem

This file has been truncated. show original

Also you can join our matrix room: https://matrix.to/#/#nixd:matrix.org for real-time communication & support.

573 · June 13, 2023, 9:26pm

I was able now to fully reproduce all non-flake examples from the User Guide using nvim configured with nvim-lspconfig.

Some hints:

I had to generate the .nixd.json file (called workspace configuration) via the .nixd.nix given at their site to avoid syntax errors - the User Guide explains how
In the workspace configuration I added the full path to my nix file - /tmp/test/default.nix in my case - /tmp/test/.nixd.json accordingly as workspace configuration
nvim /tmp/test/default.nix was the call that the Editor Setup page suggests but just nvim or loading from an active nvim session works as well as long as the .nixd.json lives in the same folder
completions are only triggered when the edited file produces no eval errors i. e. is syntactically sound - edit accordingly until eval succeeds again. Example: The line meta.platforms = lib.platforms.;. In case the list doesn’t pop up edit until eval is happy again i. e. meta.platforms = lib.platforms.js; and then re-trigger by replacing the .js with .. It’s a bit involved but you’ll get the hang of it. Maybe there emerge better ways.
depending on the nvim-lspconfig setup - mine is complete after dot or at least 3 matching characters - the completion list expands accordingly
in my case hovering is accessible via :lua vim.lsp.buf.hover()

Happy nixd’ing

just my 2c for others struggling <3