jokeyrhyme/nuls

Issues

• archived: LSP functionality is developed upstream

  #29 opened 10 months ago by jokeyrhyme
  0

• honor the markdown formatting in hover content, not just plain text

  #28 opened 10 months ago by jokeyrhyme
  0

• delimiter between include paths is not correct

  #27 opened 10 months ago by jokeyrhyme
  0

• proper tail-edge throttling/debouncing needed so that diagnostics/inlay hints are up to date

  #26 opened a year ago by jokeyrhyme
  0

• raise PR for vscode-nushell-lang to replace TS glue code with `nu --lsp`

  #9 opened a year ago by jokeyrhyme
  2

• go-to-definition sometimes lands on the wrong line (but correct file, at least)

  #22 opened a year ago by jokeyrhyme
  4

• depend upon and invoke upstream nushell code directly (not via spawning new `nu` processes)

  #7 opened a year ago by jokeyrhyme
  2

• donate code/project to nushell organisation?

  #3 opened a year ago by jokeyrhyme
  3

• incorporate language server directly in the upstream `nu` executable

  #8 opened a year ago by jokeyrhyme
  3

• completions are missing their kind/type

  #21 opened a year ago by jokeyrhyme
  0

• Cargo.lock should be committed

  #16 opened a year ago by colemickens
  2

• negotiate position encoding (UTF-8, UTF-16, etc) with client and handle outcome

  #10 opened a year ago by jokeyrhyme
  2

• instructions for development and use with Visual Studio Code

  #2 opened a year ago by jokeyrhyme
  1

• instructions for development and use with helix

  #1 opened a year ago by jokeyrhyme
  1