Yeah, you’re sort of fundamentally misunderstanding the relationship between a host and guest VM, here. The guest VM is an entirely different machine. It shares nothing with the host. Including shared libraries and other build chain dependencies.

instill in me a strong sence that Emacs not only coexists within the operating system, but rather embodies the operating system itself.

It just implements being a drag-and-drop target; it does not “coexist within the operating system”

While it is true that Windows does not support dragging files from dired buffer to external locations, but I seldom encounter such a requirement in my day-to-day workflows.

Windows folders support being a drop-target; this is likely emacs not supporting /its/ side of the protocol.

Ah, I see the dired-mouse-drag-files note, below.

This was asked just 5 days ago.

C-h a replace-regexp , select the function, and look at its help string.

The solution will end up looking something like:

M-x replace-regexp  : \([0-9]+\):\(.*\)  \,(+ 1 \#1):\2

But with (format-time-string) instead of my (+1 1 \#1); I don’t know time formatting functions in emacs elisp off the top of my head, sorry.

(Or use query-replace-regexp if you want interactivity.)

yes, should do. It’ll prompt you if you want to kill the existing live compilation to start the new one. If it’s already dead, it’ll just launch the new compilation.

One trick, as well, is if you rename the existing *compilation* buffer, it will live on its own lifecycle, so you rename it to *server* or whatever, and still do compilation cycles (eg. just go build main.go) while the existing main from the previous run is still live.

There’s only one running *compilation* buffer allowed at a time, so if you use M-x compile (which I’ve had bound to C-x C-e for like 20 years), that should roughly ensure it.

In the past, I also had a bit of elisp to – IIRC – create and rename multiple compilation buffers to be able to run multiple things at once (multiple servers in a control plane).