Closed abingham closed 10 years ago
Why would this require a macro? Just create a closure, using lexical bindings (either with Emacs 24 or with cl).
"Require" in this case is a code word for "I don't know much about emacs lisp" :) You're right that a closure should do the trick, but that's probably something I learned after I wrote this ticket.
It appears that the emacs xmlrpc library does not provide return values for asynchronous calls. I was hoping to return lists of modified resources for refactorings and then use these to refresh buffers, but I guess I'll need to just find some heuristic (at least for the elisp client.)
The switch to asynchronous calls has broken the support for reverting buffers after changes have been made. It would be nice if a buffer could be associated with an async call, and that buffer reverted when the call finishes. I'm not certain, but I think that this will require a macro since the async handler (likely a lambda) will need some way to "remembering" the buffer to revert. Need to ponder this...