+how to deal with swank protocol?
+- given event and a result, produce produce corresponding structure to
+to decouple the rest of plugin from swank protocol, make ISwank to
+specify a limited set of send commands, each of them can produce a bunch of
+signals - either to passed runnables or to registered listeners.
+By specification of which command produce which signals will specify
+rigit interface between lispdev and swank.
+So all infos will be swankrunnables, but result node is private,
+can be set, but cannot be read. Instead get result values through
+lispimplementation transformation functions.
+asyncExec - will call run at appropriate time
+right before calling run, locks runnable, sets value of result LispNode,
+runner class - takes in runnable and