Are you sticking to a specific version of nvim nightly for now? about nvim HOT 6 CLOSED

That's a lot of typing 😄

• Random segfault/crashes (twice a day?)
  this was the case for me, too. I even wrote on reddit with not much outcome. Since a couple of weeks I have no seg faults anymore.

• when I use :e filepath/filename
  I barely use :e for opening files... But as the error not always occurs maybe you can limit it to special circumstances? A opened special buffer,...

• I also have been seeing lag in general when typing in the command bar(?), or whatever is the proper name for the bar at the bottom.
  Also no issues but I have to admit that I went back to cmdheight=1 because I experienced a lot of glitches and unwanted behaviour with cmdheight=0. Sadly

Regarding your go question:
I think that's the whole point. Everybody's code hast the same formatting and convention (which I do like). When you are aware of options how to customize gofmt/gopls I can have a deeper look on how to inject those to the LSP's call :)

If you are just talking about disabling the warnings in the LSP I am not aware how to only disable certain diagnostics. You could however toggle diagnostics on/off with md but you loose all diagnostic info in the buffer. (in the statusline they would still appear)

from nvim.

what kind of glitches? Since a week or so it is (again) fairly stable for me
I am always running dev and upgrade almost each day so the answer is no 😄

from nvim.

Random segfault/crashes (twice a day?), but one issue I see very often is when I use :e filepath/filename I see the error

Error executing vim.schedule lua callback: ...m/site/pack/packer/start/nui.nvim/lua/nui/split/init.lua:147: Invalid window id: 1276
stack traceback:
        [C]: in function 'nvim_set_current_win'
        ...m/site/pack/packer/start/nui.nvim/lua/nui/split/init.lua:147: in function '_open_window'
        ...m/site/pack/packer/start/nui.nvim/lua/nui/split/init.lua:210: in function 'mount'
        .../packer/start/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:825: in function 'create_window'
        .../packer/start/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:947: in function 'draw'
        .../packer/start/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:1084: in function 'show_nodes'
        ...ree.nvim/lua/neo-tree/sources/filesystem/lib/fs_scan.lua:103: in function 'job_complete'
        ...ree.nvim/lua/neo-tree/sources/filesystem/lib/fs_scan.lua:125: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>

I also have been seeing lag in general when typing in the command bar(?), or whatever is the proper name for the bar at the bottom.

Sometimes see random cmdheight issues, but I guess neovim/neovim#20249 will fix those.

from nvim.

Do you happen to know if it's possible to customize the gofmt/gopls rules? I tried searching but looks like they are strongly going for convention over configuration. Currently, some package names are using underscores or camelCase and was hoping I can disable that, until I'm able to notify rest of my team, change all these incorrect package names & folders.

Sorry for typing so much, but I hope this is better than creating multiple tickets.

from nvim.

If anyone reads this for the underline / package name issue. I submitted a PR yesterday to allow you to configure go.nvim & disable it. https://github.com/ray-x/go.nvim/pull/221/files

from nvim.

@partounian nice! I think I'll use this too :) a971716

from nvim.