Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot start lsp server with neovim #393

Open
Rainboylvx opened this issue Sep 3, 2023 · 2 comments
Open

cannot start lsp server with neovim #393

Rainboylvx opened this issue Sep 3, 2023 · 2 comments

Comments

@Rainboylvx
Copy link

according to neovim doc https://neovim.io/doc/user/lsp.html#lsp-quickstart

I create a minial config lsp.lua

vim.cmd([[autocmd BufNewFile,BufRead *.asy setlocal filetype=asy ]])

vim.lsp.start({
  name = 'asy lsp server',
  cmd = {'/usr/bin/asy','--lsp'}
})

then ,i use command below

nvim -u lsp.lua hello.asy

and get error

client 1 quit with exit code 0 and signal 6

my envirment
os : archlinux

asymptote version

Asymptote version 2.87-4 [(C) 2004 Andy Hammerlindl, John C. Bowman, Tom Prince]

ENABLED OPTIONS:
V3D      3D vector graphics output
WebGL    3D HTML rendering
OpenGL   3D OpenGL rendering
SSBO     GLSL shader storage buffer objects
GSL      GNU Scientific Library (special functions)
FFTW3    Fast Fourier transforms
XDR      External Data Representation (portable binary file format for V3D)
CURL     URL support
LSP      Language Server Protocol
Readline Interactive history and editing
Sigsegv  Distinguish stack overflows from segmentation faults
GC       Boehm garbage collector
threads  Render OpenGL in separate thread

DISABLED OPTIONS:
Eigen    Eigenvalue library

@MicroTransactionsMatterToo
Copy link

MicroTransactionsMatterToo commented Oct 1, 2023

Seems to be related to #394 , the language server doesn't seem to appreciate dealing with the capability information sent by editors and segfaults when parsing the JSON. Signal 6 is SIGABRT, which is typically caused by memory allocation issues.

@johncbowman
Copy link
Member

Is this issue still present with Asymptote 2.87?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants