Re:Modd: a flexible tool for responding to filesystem change
by cortesi on Wednesday February 10, 2016 @06:57PM
(#11077211)
Neat! The idea of putting the build commands into the code as a comment is very interesting.
Re:Modd: a flexible tool for responding to filesystem change
by thwarted on Wednesday February 10, 2016 @07:10PM
(#11077270)
Not directly applicable here, because you need to work with what you have, but this kinds of stuff always reminds me of https://www.jwz.org/doc/cddb.html
Re:Modd: a flexible tool for responding to filesystem change
by cortesi on Wednesday February 10, 2016 @07:19PM
(#11077323)
Heh, I know what you mean. BTW, directly following that link from here gets you to jwz's wee joke about HN. You'll need to copy the link and paste it in a new tab to see the article.
I chose to build the commands into the file with a comment rather than add an extra config file. For your test-compile cycle for Go, I think that would look like this at the top of each of your go files:
# autorun go install ./cmd/devd
modd looks like it has the advantage of only specifying this one, and specifying commands to be run when modd first starts up (autorun only has one type of command that's run on startup and on file changes).