+This document helps only with the aspects of this binding, so reading
+the man-page and other information on the inotify-facility may be
+needed. Reading the next sections and the docstrings of exported
+symbols should get you going, otherwise the source itself may also be of
+some value.
+
+
+# REPLSHOT
+
+Macros make keeping track easier, so the following example is
+straightforward:
+
+ > (with-inotify (inotify T ("." :all-events))
+ > (loop (format T "~{~A~%~}" (next-events inotify))))
+ > =>
+ > #S(CL-INOTIFY::INOTIFY-EVENT :WD 1 :MASK (CREATE) :COOKIE 0 :NAME .zshist.LOCK)
+ > #S(CL-INOTIFY::INOTIFY-EVENT :WD 1 :MASK (OPEN) :COOKIE 0 :NAME .zshist)
+ > #S(CL-INOTIFY::INOTIFY-EVENT :WD 1 :MASK (MODIFY) :COOKIE 0 :NAME .zshist)
+ > #S(CL-INOTIFY::INOTIFY-EVENT :WD 1 :MASK (CLOSE-WRITE) :COOKIE 0 :NAME .zshist)
+ > #S(CL-INOTIFY::INOTIFY-EVENT :WD 1 :MASK (DELETE) :COOKIE 0 :NAME .zshist.LOCK)
+ > ...
+
+(Tilde-expansion has to happen at another level, else I would've used
+that.)
+
+The first parameter is (per convention) the symbol to which the queue is
+bound, the second is the parameter to `MAKE-INOTIFY`. The `&REST` list
+consists of parameter lists for the `WATCH`-function, which is called
+for every list before the `&BODY` is executed. We don't actually need
+to `UNWATCH` every watched path as closing the queue will also take care
+of that.
+
+
+# LOWER-LEVEL USAGE EXAMPLE
+
+You don't have to use macros: all functionality is available in function
+form, although some care should be taken as currently no cleanup handler
+is registered for opened queues, or rather their file handles.
+
+ > (use-package '#:cl-inotify)
+ > (defvar *tmp*)
+ > (setf *tmp* (make-notify))
+ > (watch *tmp* "/var/tmp/" :all-events)
+ > (next-events *tmp*)
+ > (close-inotify *tmp*)
+