bfredl

I hope to look into this the following days. I have read the vim implemention, but it relies heavily on the fact that vim "owns" the X11 selection, so that...

Wow. When in commandline mode, vim actually emulates the "dumb" terminal selection (I mean selecting line numbers and terminal whitespace and everything), I always thought it just turned off mouse...

@fmoralesc How, from vim? :) Well, I will start with visual mode selection as I suppose that whats most useful and simplest to implement. Implementing `autoselectml` will probably require a...

Hmm, what actually happens in vim, when visual mode and another x11 app wants to paste selection, is to save editor state,literally do `"*y` and then restore editor state so...

It seems like nvim doesn't distinguish between mouse drag and mouse release events, at least not from observing `do_mouse` (I get first `is_click, is_drag = true,false` then `false,true` but never...

Seems regression from vim, just try `:map anycommand` works in `vim` but not `nvim`. Or select window by clicking on statusline (and not dragging).

Last time I checked, `` event (which would have allowed a swift resolution of the main issue) was broken :(. Time to check again...

(I mean one could have done `vmap "*ygv` (or a builtin equivalent thereof) and basically be done with it...)

Good to know :+1: #3708 might work in the terminal in the meanwhile (even if very inefficient, and needs a rebase), but I hope to get #4523 in a testable/usable...

Yeah `on_lines` definitely should go away soon enough (at least in 0.13) > One thing is that on_range can be called multiple times for one line which I don't think...