acme-lsp

ll as adding "snippets" that can be executed with one click of the middle mouse button. Acme by itself is already plenty useful (`win` is part of the "standard distribution" so to speak, in that it is part of the various Plan9 forks and of plan9port), and a lot of extra stuff can be built rather quickly by hooking into its 9p interface: For example, my tool to add commonly used tools to the tag (the blue line at the top of each text window that contains the file name and commands that act on the window) is a handful of lines of shell script that parse entries in acme's `acme/log` file and select the appropriate tools to add based on the name of newly opened files. My Git integration is a thin wrapper around `win` and `git commit --interactive` that pops open a window that allows me to author a Git commit similar to (but a lot simpler than) magit for emacs and fugitive for Vim work. Even if you're not in Plan9 (or one of the forks), I encourage you to give [plan9port](https://github.com/9fans/plan9port)'s Acme a spin. (FWIW, this post was written in an Acme window because it's a lot more intuitive to use after some getting used to than regular ol' GTK text boxes used by Firefox.)

en middle-click `go test` again to try the tests once more. The delve debugger also prints line numbers that work with Acme. I run delve in an Acme terminal, and when I e.g. print a backtrace, I can simply right-click any of the line numbers to jump immediately to that code (Acme will open the file in question if it's not already open). acmego will run gofmt and automatically add/remove imports as necessary every time you save the file, which is a huge convenience. There's no syntax highlighting, which is a huge dealbreaker for some people. Personally, I find it distracting to watch huge swathes of my file change colors because I typed ", then change back as soon as I close with another ", so the lack of highlighting is great for me. Edit: in my sample workflow above, I mentioned typing `go test` right in the directory window, but that's just ephemeral... you'll lose the commands if you refresh the file list, etc. A more permanent thing is to drop useful commands into a "guide" file in that directory; that way you can keep a whole suite of commands to run tests, run benchmarks, build & deploy, etc. right at your fingertips. Edit 2: There's also a number of Language Server Protocol clients for Acme (see https://news.ycombinator.com/item?id=23782439 and https://github.com/fhs/acme-lsp) but I don't use them... I'm old-fashioned.