this post was submitted on 12 Oct 2023
0 points (50.0% liked)
Emacs
310 readers
2 users here now
A community for the timeless and infinitely powerful editor. Want to see what Emacs is capable of?!
Get Emacs
Rules
- Posts should be emacs related
- Be kind please
- Yes, we already know: Google results for "emacs" and "vi" link to each other. We good.
Emacs Resources
Emacs Tutorials
- Beginner’s Guide to Emacs
- Absolute Beginner's Guide to Emacs
- How to Learn Emacs: A Hand-drawn One-pager for Beginners
Useful Emacs configuration files and distributions
Quick pain-saver tip
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There's only one running
*compilation*
buffer allowed at a time, so if you useM-x compile
(which I've had bound toC-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).
Okay so what I think your saying is if i do something like this as the compilation command
Then when I run compilation again it will kill the buffer and running process and all will be good ?
In which case I wonder why you are not running go run anyway?
Probably because I was just getting into golang and following a tutorial which did not mention using go run, but I will now thanks :)
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. justgo build main.go
) while the existingmain
from the previous run is still live.Awesome I will give that a try :)