From 828adac48d0e08766d192c7ce01021083cfc4d67 Mon Sep 17 00:00:00 2001 From: Christopher Vogt Date: Sun, 12 Mar 2017 22:00:00 -0400 Subject: fix file watching for real last file watching update didn’t work well enough. This now - rips out barbary watch service as it seems buggy crashing the jvm - make cbt exclusively write files to watch to a file - uses fswatch instead watching all files in that file MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index 205cc6e..cad92c9 100644 --- a/README.md +++ b/README.md @@ -203,7 +203,8 @@ As you can see it prints `asdf`. Adding tasks is that easy. ### Triggering tasks on file-changes -When you call a task, you can prefix it with `loop`. +When you call a task, you can prefix it with `loop`. You need to +have fswatch install (e.g. via `brew install fswatch`). CBT then watches the source files, the build files and even CBT's own source code and re-runs the task when anything changes. If necessary, this forces CBT to re-build itself, the project's dependencies and the project itself. @@ -220,6 +221,11 @@ you managed to change windows back from your editor to the shell. Try changing the build file and see how CBT reacts to it as well. +To also clear the screen on each run use: +``` +$ cbt loop clear run +``` + ### Adding tests The simplest way to add tests is putting a few assertions into the previously -- cgit v1.2.3