Well this is scary. Was coding some Go in neovim and noticed that some buffers for some reason had weird changes. Changes that I did not introduce.
Turns out something is very wrong and I cannot figure out the source of issue. Either LSP or something, but after some idle time some of the open buffer are garbled with edits.
And all this on fresh #neovim v0.12.1. Anyone seen something like this? Where to even start debugging this? #LSP config, #gopls?
[Перевод] Go исполнилось 16 лет: главное о развитии языка и экосистемы
Команда Go for Devs подготовила перевод статьи о том, как Go отмечает шестнадцать лет в Open source. От новых инструментов для тестирования и профилирования до модернизаторов кода, MCP и прорывов в производительности — язык переживает один из самых насыщенных периодов развития.
https://habr.com/ru/articles/966700/
#Go #Go125 #GreenTea #synctest #контейнеры #gopls #MCP #ADK #криптография #производительность
Early this year I filed an issue in the #delve debugger repo about how some type names were displayed not by their name but their fully "resolved" path: https://github.com/go-delve/delve/issues/3910
As trivial as that may seem, it makes debugging almost useless for the deeply recursive #golang code I normally work on when all you see is incredibly long strings cluttering up the view.
I had almost forgotten about this until another issue I filed in Go's #gopls tool ( https://github.com/golang/go/issues/73661 ) got fixed, but the fix came with another issue... I'm sure you can guess which one.
I had previously assumed that type names getting "expanded" to paths was an oversight where it occured, but it seems like pretty printing type names in Go is a non-trivial problem: https://go-review.googlesource.com/c/tools/+/671915/1..3/gopls/internal/analysis/modernize/slices.go#b192
Hi there, and thanks for providing this tool! Using Delve DAP via VS Code, I'm working on some deeply nested data structures. While the first level of bindings have their type information displayed...
TIL that go language server gopls can generate the boilerplate for a unit test of a function.
[4/5]
jose-elias-alvarez/typescript.nvim - easy #typescript-language-server integration (I've just seen this is now archived, but it still works well.)
fatih/vim-go - #golang language support
mhartington/formatter.nvim - format runner. I use it to run #biome and #gopls to auto-format code.
*GIT*
tpope/vim-fugitive - THE BEST. This is how I mostly interact with #git.
lewis6991/gitsigns.nvim - git decorations for the gutter
rhysd/conflict-marker.vim – makes resolving merge conflicts easier
[3/5]
tpope/vim-commentary - comment macros for various languages
tpope/vim-surround – another one from vim plugin god @tpope. Easily delete, change and add surroundings like quotes, parens etc. in pairs
neovim/nvim-lspconfig - configs for the neovim #lsp client. lsp integration is one of the two reasons I switched to #neovim (the other being #treesitter). Integrates #typescript, #biome, #gopls and #tailwindcss language servers.
sheerun/vim-polyglot - collection of language packs
#gopls v0.13.0 will be released next week. See what is coming.🎁🕊️
https://github.com/golang/tools/releases/tag/gopls%2Fv0.13.0-pre.3
Please give it a try and give us feedback. 
These are release notes for a prerelease version of gopls. v0.13.0 will be released soon, but please try the prerelease if you can! go install golang.org/x/tools/[email protected] This release f...
Configured gopls with lsp-mode in Emacs. Jump to definition and auto completions work blazing fast now. Checkout https://github.com/golang/tools/tree/master/gopls and https://emacs-lsp.github.io/lsp-mode/
Wind (Vējš)
Habr
Anders Eknert
Michal Vyskočil
data0
Hana
Bhavin Gandhi 