Lua Development for Neovim

README
Issues 12

Closed

Make cmd configurable

I'm using neovim-0.5 beta from ubuntu ppa. the function that determines cmd value by default uses jit.os . But jit.os is not available in global namespace in my neovim . So the plugin fails to load . Making cmd a configurable option solves any issue regrding that specific function .

The change is minimal it now checks if cmd was passed with the setup call if it was it uses the cmd value that was passed otherwise uses its default function to determine cmd value.

This small change gives more control to user to determine what command is executed to start the lsp server.

opened Nov 3, 2020 by shadmansaleh 9

Closed

My Lua plugin, which doesn't do anything fancy, breaks nlua.nvim's diagnostics

When I enable git-blame.nvim, diagnostic messages don't show up in Lua files/projects. When I open a Lua file that is not in a Git repo, diagnostics work. After disabling git-blame.nvim, diagnostics also work. I have no idea why this would happen. git-blame.nvim and sumneko_lua work fine together.

Here's how I set up nlua:

require'nlua.lsp.nvim'.setup(lsp, {
    on_attach = on_attach,
    globals = {'love'},
    disabled_diagnostics = {'lowercase-global'}
})

And default sumneko_lua:

lsp.sumneko_lua.setup {on_attach = on_attach}

My on_attach:

local on_attach = function(_, bufnr)
    require'completion'.on_attach({
        sorter = 'none',
        matcher = {'substring', 'exact', 'fuzzy'}
    })

    -- Mappings
    vim.api.nvim_buf_set_keymap(bufnr, 'n', 'gD',
                                '<Cmd>lua vim.lsp.buf.declaration()<CR>',
                                keymap_opts)
    vim.api.nvim_buf_set_keymap(bufnr, 'n', 'gd',
                                '<Cmd>lua vim.lsp.buf.definition()<CR>',
                                keymap_opts)
    vim.api.nvim_buf_set_keymap(bufnr, 'n', 'K',
                                '<Cmd>lua vim.lsp.buf.hover()<CR>', keymap_opts)
    vim.api.nvim_buf_set_keymap(bufnr, 'n', 'gi',
                                '<cmd>lua vim.lsp.buf.implementation()<CR>',
                                keymap_opts)
    vim.api.nvim_buf_set_keymap(bufnr, 'n', '<C-k>',
                                '<cmd>lua vim.lsp.buf.signature_help()<CR>',
                                keymap_opts)
    vim.api.nvim_buf_set_keymap(bufnr, 'n', '<leader>D',
                                '<cmd>lua vim.lsp.buf.type_definition()<CR>',
                                keymap_opts)
    vim.api.nvim_buf_set_keymap(bufnr, 'n', '<leader>rr',
                                '<cmd>lua vim.lsp.buf.rename()<CR>', keymap_opts)
    vim.api.nvim_buf_set_keymap(bufnr, 'n', '<leader>e',
                                '<cmd>lua vim.lsp.diagnostic.show_line_diagnostics()<CR>',
                                keymap_opts)
    vim.api.nvim_buf_set_keymap(bufnr, 'n', '<leader>ca',
                                '<cmd>lua vim.lsp.buf.code_action()<CR>',
                                keymap_opts)
    vim.api.nvim_buf_set_keymap(bufnr, 'n', '<leader>cd',
                                '<cmd>lua vim.lsp.diagnostic.set_loclist()<CR>',
                                keymap_opts)
end

I initialize the lsp variable at the top of init.lua:

local lsp = require('lspconfig')

Maybe you have some ideas about why this would happen?

opened Dec 9, 2020 by f-person 2

Closed

Quickfix list, populated with file's first line, opened after keypress `gd`

After pressing gd, it successfully directs me to the correct file. However, it will open a quickfix list populated with file's first line which I assumed it is not intended since previous action doesn't lead to this behaviour.

Actual behaviour

https://vimeo.com/576117758

Expected behaviour (similar with `gf` but slower):

https://vimeo.com/576118265

Using Neovim 0.5.0 and Arch btw

opened Jul 17, 2021 by ingram1107 1

Closed

correct name and case for macOS

I didn't test this yet, but the sumneko bin folder for Macs is "macOS" and jit.os() returns OSX.

opened Feb 8, 2021 by klooj 1

Closed

Rename nvim_lsp to lspconfig

neovim/nvim-lspconfig#348

opened Nov 16, 2020 by willelz 1

Closed

Allow passing of callbacks

Are there other parameters that can be passed to the nvim_lsp.sumneko_lua.setup function? If so then could also just do a vim.tbl_extend('force', config, { ... }) or similar so that they don't all have to be listed explicitly.

opened Oct 4, 2020 by smolck 1

Open

Is this plugin remap the 'K'

for my neovim keymap, I remap the K for <C-d> after I install this plugin, I step into the help-doc when I use 'K' for scrolling, How can I fix that?

opened Nov 23, 2022 by JuanZoran 0

Open

isdirectory evaluation

https://github.com/tjdevries/nlua.nvim/blob/a0722bd2f6fdf54f85aaf8dcd6a1032f64c83905/lua/nlua/lsp/nvim.lua#L32

should be isdirectory(...) == 1 or all will be added

opened Sep 12, 2021 by yatli 0

Open

question on 'gf' package.path/include_expr

thank you for this v helpful plugin.

with the following hiearchy:

nvim/
  - init.lua
  -  lua/
    - domain/
      - file.lua

a line in file init.lua says "require('domain.file')". If I cd nvim/ && nvim init.lua and then gf on that line, nvim opens an empty buffer. But, if instead I cd nvim/lua/ then gf works exactly as expected.

This difference is because nvim/lua/ is not in my package.path. My question is, should it be (and i'm failing) or is this expected?

opened Apr 16, 2021 by klooj 0

Open

Fixed download_sumneko.lua script

Resolves #20

opened Apr 16, 2021 by luishgh 0

Open

lsp: more config opts, macOS binary correction

This corrects the binary location on macOS and makes the sumneko setup a little more configurable; the latter gives more flexibility for hacks or those who do not use your install script. I left some comments in there about things I added and one minor todo.

If you want to merge this lmk and I'll write some quick documentation for the config. Otherwise, I'll just use the fork for me.

opened Mar 29, 2021 by klooj 0

Open