-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
change registery when replacing placeholder #175
Comments
You should describe the example. |
Sorry about that. For example: given the following snippet: "body": [
"```${1:lang} ",
"$0",
"```"
] When expanding it the cursor goes to lang placeholder, when I change it, my main vim registry gets replace with |
The example is better, but I don't understand why the feature fixes your problem. |
Okay, Say I have this in my main registry type KeyProduct struct{} When I write The desired behavior is that when I replace |
Ah I get it. This is the feature of replace. It is hard to fix... |
And the "registory" should be "register" in Vim word. |
I'm having the same issue. I think we can have two possible solutions:
I had used solution 1, It's a bit hackish (clever?) but got some problems with other plugins and it polluted the mappings, so I'm evaluating other solutions. Personally, I would like 2 (is more flexible and powerful). But I'll understand if it's not something the maintainers would like to add to the codebase. EDIT: A third option, but not optimal: add an explicit mapping to delete the text and send it to the blackhole register before writing the replace text: snoremap <silent> <c-h> <c-g>"_c So when you have |
Interesting, this looks clean and simple, @hrsh7th any chances this can be implemented? For now I will try to adjust to Thanks @davidsierradz |
hey @hrsh7th, is there a way to change the registry when replacing the placeholder. I was so annoyed for sometime now that I'd need to skip replacing the placeholders because it means I will lose what I have in my main registry .
Thanks
The text was updated successfully, but these errors were encountered: