1y ago

Any suggestions for a Kill Compile Run Execute sequence from emacs in a single step ?

Is there a way I can compile then run my compiled application, if its already running then exit recompile and run.

So current work flow is compile switch to terminal run binary, switch back make changes compile return to terminal Ctrl + C to kill then run again, be nice if I could do all this from inside emacs.

I guess a bash script could be an option but curious if others have this work flow and how it works ?

Currently in a golang workflow but even better if there is a generic solution.

You're viewing a single thread.

10 comments

Maybe do it all in the makefile? Then use projectile or something to "make"...
- I did wonder if that's perhaps the solution, although not sure how you would get the pid in a make file to kill the running instance, make files are not something I have played with much, I will see if others have any suggestions.
  
  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).
  
  Okay so what I think your saying is if i do something like this as the compilation command
  
  go build main.go && ./main
  
  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. just go build main.go) while the existing main from the previous run is still live.
  
  Awesome I will give that a try :)

10 comments