While I think I create empty sbt project that uses sbt
0.13.13, I guess "Create empty sbt project" will be better.
2)For me the biggest advantage of this article that it is easy to
reproduce, and I think it was your goal. You showing advantage of sbt '~run', while you didn't mention that user needs to open new tab to try 'sed' source file, some confused user may try to do it in the same terminal session, and it wouldn't work for him,
➜ new-project sbt '~run'
[info] Loading project definition from /home/vol/new-project/project
[info] Set current project to new-project (in build file:/home/vol/new-project/)
[info] Running SimpleApp
It definitely definitely works
[success] Total time: 0 s, completed Dec 22, 2016 8:54:43 AM
1. Waiting for source changes... (press enter to interrupt)
sed -i -e 's/works/definitely works/' \
➜ new-project src/main/scala/SimpleApp.scala
And we leave sbt, when we paste the sed code. (this who don't like to watch video)
You also may mention where to exit the sbt.
3) I think the snapshot about directory and file states will be great for text version.
The idea seems great, thank you for '~run' and '~test', I use sbt for a year but don't know about this feature. What I like most about this article, that sbt looks super simple when you go throw this steps.