Clojurians Log v2

Ah, cursorDx isn't really documented. I was wondering what it should be.

@snoe You gonna fix, or should I make a pull request?

pull request would be great

ok, I'll do it tomorrow

@eraserhd is there any demo or introduction for avi in detail. I wonder those advantages it provides

@doglooksgood Not really. I'm not sure there are any advantages yet 🙂

Unless being written in Clojure is an advantage.

So far, it's been implementing basic features of Vim - normal mode, basic commands, and so forth.

But it's getting close to the place where I'm going to do fun things that I want to do, like subset buffers, structural editing, and so forth.

@snoe What the heck is @ in -strlen(@-)?

Oh, register contents?

yeah, it's supposed to capture the last single line change - reading more last night made it seem like that's not exactly what's needed for dx (and it's persistent across buffers which is what you're probably seeing when you pair)

I'm search for a develop environment that running as a server and provide the full features for clojure development(REPL, instaREPL, debugger, code completion, definition lookup, structural editing) 😂

@snoe Yeah, I read that v:operation could be left over from something else, and that ex-mode commands don't set it. But also @- could be left over.

This makes figuring out what actually happened interesting.

I'm thinking about it, and am willing to put in some elbow grease here. Have any ideas?

@doglooksgood yeah, Avi has no code completion or any kind of REPL yet or documentation lookup (because I can mostly work around these things with tmux). Structural editing is super important, but not started. I have a general framework in mind that should allow anything structured. Also Code Bubbles was an IDE that I saw a demo of that blew me away, and I hope to implement some of that.

@eraserhd I've pretty much just learned vimscript to implement the parinfer plugin so I'm not sure I can add too much. I had been thinking about saving the previous buffer in the cljs code but it would be nice if vim could just tell us how much was changed. stackoverflow suggests that '[ and '] may work http://vi.stackexchange.com/questions/8029/from-a-textchanged-autocommand-event-how-to-get-the-range-that-has-been-changed

oh, and https://github.com/neovim/neovim/issues/1114 is something that I thought would be a way to use the api over TextChanged

@snoe Ah, good stuff!

FYI, I'm not very good at vimscript either, though I guess I've learned a little bit.