> As for motions, what kind of motions do you think are difficult to create? It's mostly text objects. Text objects for scope, variable references, etc. I thin

> As for motions, what kind of motions do you think are difficult to create? It's mostly text objects. Text objects for scope, variable references, etc. I think there are motions I have not yet discovered that operate on syntax trees. These are nonlinear the way surround is nonlinear. I was introduced to multiple selection and generalized cursors when one of the DabbleDB guys implemented a generalized cursor editor. I thought it was awesome and did a bunch of research: http://static.usenix.org/events/usenix01/full_papers/miller/miller_html/ http://static.usenix.org/events/usenix01/full_papers/miller/... http://scholar.google.com/scholar?q=related:7040sK6UgeAJ:scholar.google.com/&hl=en&as_sdt=0,33 http://scholar.google.com/scholar?q=related:7040sK6UgeAJ:sch... After reading a bunch, I got around to thinking what I'd have to do to implement an editor that could handle generalized cursors based on my experience with vim and hacking on it. I came up with the idea for an edit core consisting of motions as compositions of partially applied functions. Takes a position returns a list of ranges, applying the list of ranges to an operator produces an edit. The jump from there to regions is pretty straightforward. The system also provides a clear path to how keyboard mapping would work (along with stealing the context ideas from ST). I'm unaware of an editor that works this way but I find it difficult to believe I'm the first person to think of this. If I can successfully maneuver my job into building web development tools, I expect to gut Codemirror and replace the core operations with these primitives as a top priority but I haven't gotten there yet. For context sensitive stuff: You can do clever stuff with it. As an example, if you're in a JSON file, after an identifier, and you type a : the editor can automatically put quotes around the key if it's not already quoted. My intro to the usefulness of context sensitive keys was that the ruby textmate bundle would insert Ruby interpolation (#{|} with | for cursor) when you hit # in a string.