Maximilian Bosch

Not an emacs expert, but it seems as if the issue can be mitigated by declaring e.g. `(setq lsp-idle-delay 0.500)` (see https://emacs-lsp.github.io/lsp-mode/page/performance/). Would you mind checking if that's the case?...

Last time I looked I wasn't too fond of it, but that was a few weeks ago, so things might've changed. Anyways, this is IMHO reasonable, but I don't have...

Why did you close this?

I'm happy to take a look during the next days :)

Wait.... I think... I can reproduce the memleak, realiably :tada: (and I kinda feel dumb now :D) I halted both affected `rnix-lsp` processes with `gdb` on my laptop for now...

@nrdxp may I ask if you intend to finish this? Otherwise I'd take care of it when i'll get to it :)

> If not, I'll schedule it for this weekend If you still have the capacity, feel free to finish :) I wouldn't have managed to take care of it last...

I think it'd be a bit harsh if we only show the attr-set when hovering on the closing/opening bracket in an expression like ```nix { foobar = 1; } ```...

I think we should also make a plan when/what to release: * I'm not sure how much has changed since 0.1.0 (I'm using git revs of this repo locally), but...

As discussed with @aaronjanse via DM, we'll proceed here like this: * [0.2.0](https://github.com/nix-community/rnix-lsp/milestone/1) will be released when we've stabilized `master`. I think there are a few new useful features on...