[Feature] <del> should not occupy + register

[gilbh]

Hi,

When I mark a in EDIT VISUAL and then hit d, the text is inserted into the + register (the Windows clipboard). This causes confusion because it will replace whatever is already in the clipboard. One way of getting over this is simply using <win-v> instead of <ctrl-v> because it will show the history of previous clipboard content, but I am wondering if you would consider differentiating between d (which should not occupy the + register, as in DEL operation) and x (which is somehow akin to <ctrl-x> and therefore is a more natural candidate for CUT operation). This way, the user can decide between DEL and CUT ... As far as I see in the vim documentation, there is no difference in VISUAL MODE between d and x -- so you can make a distinction here without breaking anything assumed in vim ...

Let me know what you think.

Best.

[pit-ray]

Thanks for the idea.

Since the current win-vind have no register, I will probably start with implementing it. Then we can use the syntax "{register} of Vim. And then I think it would be better to change the default registers with map.

What do you think?

Thanks.

[gilbh]

I think having registers for vind is very robust, but are you aware of <win-v>? It is a simplified idea of multiple registers for Windows, but it works well and quite useful. So I am not sure if having an additional implementation of registers is needed/useful. (It also seems like a lot of work!!).

According to Vim documentation: visual, the mappings for d and x are exactly the same (that is, both perform delete) and that is why I though the simplest solution is to have d not touch the clipboard (as in DEL) while x (which is similar to the CUT shortcut <ctrl-x>) make the clipboard insertion.

[pit-ray]

I thought <win-v> was just a clipboard history of a single clipboard. Is it possible to use it as multiple clipboards?

I understand that it is easiest to use d as a black hole register "_ and x as an external register "+,"*, but I would respect the original Vim and implement it as multiple registers if possible. Only if the implementation difficulty is high, I will use the current single register system and your idea for d and x. However, after consideration, I may change it.

Thanks.

[gilbh]

Yes, I think what you describe here makes sense.

Also, you are right that <win-v> is a history of a single clipboard and not multiple, but it does allow you to retrieve content from past clipboards and in that sense can work with win-vind because the previous clipboard are still accessible in sequence, like vim rotates "1, "2, etc.

[pit-ray]

I see. I understand. I make it open for the milestone.