[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#706458: ITP: inotify-hookable -- blocking command-line interface to inotify

On Thursday 02 May 2013 11:29:58 Goswin von Brederlow wrote:
> How is that better than the existing inotify shell tools? What do they
> lack and why not improve them instead of writing a new one?

inotify-hookable main advantage over inotywait are:
- you can specify command to run after watch as option. 
- watch are restarted
- when watching a directory, inotify-hookable ignore emacs 
  and backup files by default.
- you can specify different commands to run depending on which
  files was changed 

inotifywait is better suited to be used within a shell script.

inotify-hookable is better when you just want to run something on the command 

I currently use the following command to compile a bunch of less files into a 
css file. The css file and the less file are located in the same directory:

inotify-hookable -w . -i '.*css$' -c '../../enyo/tools/lessc.sh ./package.js'


 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Reply to: