appending text to register instead replacing existing text in buffer

[keshavbasanwal]

I wanted to cut and paste text from a helix 'buffer A' to another 'buffer B', but moving from 'buffer A' for selecting then deleting and then moving back to the 'buffer B' to paste and then again moving back to 'buffer A' seems like too much work, I wanted to ask if there is a way for me to append to registers, is there a key or command that does it?

for Example

If I press capital D after I a make a selection, then it should delete and yank it to the primary register, and afterwards if I delete another selection using capital D, it should add to the content of the the primary register, so I can paste it all in one go.

thnks

[rockboynton]

I don't think that functionality exists exactly as you describe however I can try to offer a couple other solutions that may help you achieve a smoother workflow here.

1. Do all your selections at once using s with some regex, then use :yank-join to get all selected, A-d to delete without putting text in register, then move to your other buffer and paste with p.

2. This is more what I do more generally. I have two buffers open side by side with a split. I have a keybind to easily jump between them:

[keys.normal]
H = "jump_view_left"
L = "jump_view_right"

Then I just do you describe where it is "too much work" except much faster with the split and keybind

I know it's not exactly what you were hoping, but hopefully it helps you regardless. Maybe what you're asking could be some feature in the future

[keshavbasanwal]

Thanks for taking interest in my query.

1. It is not possible for me to use first workaround because - I am using it understand how rust projects work, I am cloning popular rust projects of small sizes and de-modularize them by writing all code in main.rs then I try to modularize it myself.
2. I already have those key-binds (Super useful).

I searched and found that neovim provides similar functionality with capital registers but not in the way I want.

I will try to figure out a macro that can replicate this behavior.

Should I try to put this as an Idea for a feature-request? but I don't know if it is useful enough to be taken for consideration for a feature.

thanks man, I really appreciate you sparing time to write this answer.