Ah. Maybe a plugin thats set to start with LC that listens to a socket? Or checks an env variable ever so often, or a file for changes, or a combination of these such as hit a listening port in your plugin and check a file/var whatever.
As for the multiple instances problem, if you go with the plugin route, could have it create a tmp file to indicate running status, delete it on close so you know whether to start up rev or not. Both :) I'm exploring your suggestion of using Fossil for documentation. Normally it displays stuff in the default browser - but you can set it up so that it instead calls a browser of your choice. I'd like to set things up so that a shell call would get an already open copy of Livecode to pass a message to a handler - just like you do with AppleScript events - but something that would work on other platforms. _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
