1 you can just do square --bundle . --watch and it will compile both the min and the dev with the exact same contents.
2 i'm currently working on that in the development branch, I was thinking of adding either a new command line flag so you can get a bundle->compiled filename mapping in a seperate file, or automatically add a new key to your square.json file so you can read that in instead of having another file for this.

3 you can override the extensions that are watched in the configuration:

{
  "configuration": {
    "dist": "/www/site/output/pewpew.{ext}",
    "watch": [] // empty array to watch all the files, or an array with file extensions to watch
    }
  },
  "bundle": {
   .. your files ..
  }
}

4 There is no such option, what you would want to configure there?
5 I would just use the provided @import support from the pre-processors if they support it and use the // [square] directives for files that do not support this behavior.

Thanks for answers.

1. Problem with having dist as string (meaning dev and min will compile to the same file) if that I really want to have separate dev and production build and in production build want to use md5 as part of file name what when using currently in watch mode produces lots of files. Created quick patch locally which creates min build only when node env is 'production' to overcome that issue. Additionally noticed that dev build isn't processed by plugins, is it by design?
2. Great. In perfect world I'd like to have in dev mode only compilation made no concatenation and manifest produced, but square currently doesn't work that way, but can live with that. Could you point me where is the best place to put such logic in square? I'd like to try to do this myself.
3. Does this work in master branch? I have coffee and stylus files in on bundle and when watching it watches only for coffee files, or I'm missing something?
4. For example stylus url functionality (http://learnboost.github.com/stylus/docs/functions.url.html) , currently no way to register it except of modifying source.
5. Thanks !

Thanks for answers once again!

Cheers,
Tadek

1. This is already possible, instead of using a string in the diet configuration field you can supply it with an object (see the snippet I posted above). This way you can have different output directories and names depending on the distribution.
2. Fixing that would be to hard, you probably need to check if layers array has a length before we call the https://github.com/observing/square/blob/master/lib/square.js#L570 iterate function
3. Yes this already works in master. And I think the problem for you is square is currently configured to only build one extension at a time. Stylus compiles to CSS and Coffee to coffee script so for the time being you probably need to start 2 watching instances, one without --extension css and one with it.
4. Hmz, I haven't really thought about that and how I should handle that.. I could probably add another field to the square.json files with the name pre-processors where you can specify options per preprocessor.. This definitely something that needs to be fixed. I'll add it to the todo list for the next release.

Thanks.

1. But in that case both prod and dev files will be created what means lot of files in dev/watch mode.
2. Thanks, I've forked square and add some quick hacks to make it usable for my purposes
3. Overcomed it in very hacky way in my fork
4. Thanks !