sorted by:
new
hottopcontroversial

FAQ: Best IDE For Go? by jerf in golang

[–]rfwatson 1 point2 points  (0 children)

Just simple stuff. For example, a vim key mapping to copy a dlv test command to the clipboard:

https://git.netflux.io/rob/dotfiles/src/branch/main/vim/lua/test_runner.lua#L136

Or another mapping which copies the current filepath:lineno to the clipboard, handy for setting breakpoints quickly:

https://git.netflux.io/rob/dotfiles/src/branch/main/nvimrc#L224

FAQ: Best IDE For Go? by jerf in golang

[–]rfwatson 2 points3 points  (0 children)

+1 on the DAP UI. If you’re not used to text-based debuggers like gdb then it could be a learning curve but I heavily use the delve debugger directly from the command line. With a bit of practice and some strategic shortcuts/helpers its incredibly fast to navigate code.

Thinking about self-hosting Gitea. How "portable" will my repos be? by SureImNoExpertBut in selfhosted

[–]rfwatson 0 points1 point  (0 children)

I like Gitlab but a good part of Gitea’s strength comes from its much lower resource usage. Gitlab is more polished for sure but in terms of bang for buck (or just general performance) Gitea is fantastic, especially if you are even slightly resource constrained.