How to disable linting for Iced buffer/stdout

[formsandlines]

I just wanted to share a code snippet for nvim config that might help some people who would also like to disable the unhelpful, annoying linting in the Iced buffer/stdout.

It was originally suggested by @liquidz in this issue comment for vim-lsp (which I don’t use and thus cannot verify, but surely it’ll work):

call iced#hook#add('connected', {
      \ 'type': 'function',
      \ 'exec': {_ -> lsp#disable_diagnostics_for_buffer(bufnr('iced_stdout'))},
      \ })

I have adapted it to Ale (using clj-kondo) like this:

call iced#hook#add('connected', {
      \ 'type': 'function',
      \ 'exec': {_ -> ale#toggle#DisableBuffer(bufnr('iced_stdout'))},
      \ })

And to CoC (to use with clojure-lsp, which integrates clj-kondo) like this:

call iced#hook#add('connected', {
      \ 'type': 'function',
      \ 'exec': {_ -> CocAction('diagnosticToggleBuffer', bufnr('iced_stdout'))},
      \ })

[liquidz]

@formsandlines Great!
Would it be useful to add this to the document? (e.g. tips)

[formsandlines]

For me it certainly would have been useful, I don’t know if it is much of an issue for other people though.

A problem could be that the function calls used in the snippets could differ with changes in the linting libraries, so docs would have to be updated if that happens. On the other hand, interface changes should not be so frequent so I guess it is fine if people just report when changes happen.