i.e. settings for whether or not the FSI Listener is turned on. These should be
persisted with some sort of settings file. The settings file should be
generated on the fly if not present, this will allow easier in-place update of
new versions of FsEye without overwriting existing settings files (i.e. FsEye
should not be distributed with a pre-made settings file).
Original issue reported on code.google.com by
stephen....@gmail.comon 13 Apr 2012 at 7:14