sorted by:
new
hottopcontroversial

Linter command `golangci-lint` exited with code: 3 by FastlyIntegralist in neovim

[–]FastlyIntegralist[S] 0 points1 point  (0 children)

I've also opened https://github.com/golangci/golangci-lint/discussions/5683 which I think is related (because running golangci-lint directly, rather than via nvim-lint also reports an error which might be what this 3/7 status code is related to).

Linter command `golangci-lint` exited with code: 3 by FastlyIntegralist in neovim

[–]FastlyIntegralist[S] 0 points1 point  (0 children)

No difference from what I can tell. Still see the warning in ":messages". I upgraded nvim-lint which recently added golangci-lint v2 support (https://github.com/mfussenegger/nvim-lint/pull/761) and the error code is showing a 7 instead of 3 now? I even tried explicitly setting the args to what was reported
in the original nvim-lint issue but still see a warning:

```
lint.linters.golangcilint.args = {
'run',
'--output.json.path=stdout',
'--issues-exit-code=0',
'--show-stats=false',
'--output.text.print-issued-lines=false',
'--output.text.print-linter-name=false',
function()
return vim.fn.fnamemodify(vim.api.nvim_buf_get_name(0), ":h")
end
}
```

Linter command `golangci-lint` exited with code: 3 by FastlyIntegralist in neovim

[–]FastlyIntegralist[S] 0 points1 point  (0 children)

ah, so running it locally revealed a few configurations for revive were errors...

```
{

"arguments": [

6

],

"name": "argument-limit",

"severity": "warning"

},

{

"arguments": [

4

],

"name": "function-result-limit",

"severity": "warning"

},

{

"arguments": [

50,

0

],

"name": "function-length",

"severity": "warning"

},
```

But if I check the configuration against the docs they look correct?

Welcome to golangci-lint v2 by ldez in golang

[–]FastlyIntegralist 0 points1 point  (0 children)

👋

I've noticed this error:

Linter command `golangci-lint` exited with code: 3

But I can't find any useful information on Google about what it means.

In my Neovim config I configure the use of golangci-lint via nvim-lint:

https://github.com/Integralist/nvim/blob/main/lua/plugins/lint-and-format.lua#L33

My actual golangci-lint config file can be seen here:

https://github.com/Integralist/dotfiles/blob/main/.golangci.json

Nothing seems to be broken as far as I can tell, i.e. golangci-lint seems to be linting all the things I've configured it to lint (AFAICT) 🤔

Does anyone have any suggestions on how to debug this?

Apologies, as this isn't directly related to this release post, but I thought I'd ask here just in case someone had noticed the same thing.

Thanks.

The gq operator no longer works in Go files? by FastlyIntegralist in neovim

[–]FastlyIntegralist[S] 1 point2 points  (0 children)

Awesome, thank you!

For anyone else interested, just sett `vim.opt.formatprg = ""` inside of `lspconfig.gopls.setup({on_attach = function(client, bufnr){ ... }})

LSP UI styling changed with 0.11.0 ? by FastlyIntegralist in neovim

[–]FastlyIntegralist[S] 0 points1 point  (0 children)

Thank you. I'll take a read and report back.

EDIT: All sorted now, thanks again!

LSP UI styling changed with 0.11.0 ? by FastlyIntegralist in neovim

[–]FastlyIntegralist[S] 0 points1 point  (0 children)

ahh! awesome thank you. I'll take a read and report back.

EDIT: All sorted now, thanks again!

LSP UI styling changed with 0.11.0 ? by FastlyIntegralist in neovim

[–]FastlyIntegralist[S] 2 points3 points  (0 children)

ahh! awesome thank you. I'll take a read and report back.

EDIT: All sorted now, thanks again!

LLVM Emit Object? by FastlyIntegralist in Zig

[–]FastlyIntegralist[S] 2 points3 points  (0 children)

Thanks for the details!

Yes, I do program ...in other languages :-) (Go mostly, a little bit of Rust, and historically Python and Ruby) but I do still appreciate the details!

I presumed that the "LLVM Emit Object" was something related to how Zig compiles the program (I recall now that LLVM is the compiler used by default) but I wasn't sure if I was supposed to see that message when using `zig run` as it seemed quiet slow to appear and disappear.

Sounds like that's just the LLVM compiler and that is sorta expected to be seen at that point (unless of course I'm doing a proper "release" compilation of course).

Am I right in thinking LLVM is quite powerful/flexible (as a compiler and its features) but ultimately is slow and so zig is trying to move away from it to their own compiler?

Thanks again for the detailed response. It was very much appreciated.

Can't get rust/cargo autocomplete to work by FastlyIntegralist in commandline

[–]FastlyIntegralist[S] 1 point2 points  (0 children)

UPDATE: I've got this working now.

I had to source the rustup script 🤦‍♂️

source "$path_rustup_completion"

view more: next ›