Configure asm-lsp installed with mason (nvim)

[kartoffelkopp8]

Hi everyone,

I’ve installed asm-lsp using Mason in Neovim, but I’m having trouble configuring it to work properly for NASM assembly on x86/x86-64. I want to use asm-lsp for syntax checking, autocompletion, and other LSP features for assembly files (.asm).
What I’ve Done:

Installed asm-lsp via Mason:

MasonInstall asm-lsp

The installation was successful, and I can see asm-lsp in :Mason.

My assembly files are primarily written for NASM in the x86/x86-64 instruction set.

I added the following configuration to my init.lua file:

return {

"neovim/nvim-lspconfig",
opts = {
---@type lspconfig.options
servers = {
asm_lsp = {
cmd = { "asm-lsp" }, -- Der Befehl zum Starten des LSP-Servers
filetypes = { "asm", "S", "s" }, -- Unterstützte Dateitypen
root_dir = require("lspconfig").util.root_pattern("*.asm", "Makefile"), -- Root-Verzeichnis anhand von .asm oder Makefile
settings = {
asm = {
assembler = "nasm", -- Setze NASM als Syntax
instruction_se = { "x86/x86-64" }, -- Unterstützte Architekturen
},
},
},
},
},
}

Issues:

asm-lsp doesn’t seem to work as expected:

   the first line is always marked with a syntax error,
    No further syntax checking or diagnostics appear.
    Autocompletion DOES work.

Questions:

How do I properly configure asm-lsp in Neovim with Mason for NASM and x86/x86-64?
Do I need additional configuration in the cmd or settings section for lspconfig?
Is there a way to specify the assembler (e.g., NASM) and instruction set directly in the asm-lsp configuration?
Are there any additional steps or dependencies I need to install for asm-lsp to work with NASM?

[WillLillis]

Hi! The incorrect diagnostics you're seeing on the first line is because by default, the server invokes gcc without any arguments on your source file. In order to properly provide diagnostics, you need to provide some instructions to the server on how to build your code. If you're installing through Mason, you likely have a copy of the 0.9.0 release. This version supports a compile_commands.json/compile_flags.txt file (see the project's README for further info and links) in your project's root directory. If you're able to install off of the latest master branch, there are a lot more options to customize the server's diagnostic behavior via a .asm-lsp.toml file. Using a build off of the master branch also allows you to invoke asm-lsp gen-config from the command line to create such a config file interactively. This should get you started with a few options, but if you need any further guidance please let me know :).