Skip to content
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

Feature Request: Flush writeInstructionsFile on change #54

Open
bmalinconico opened this issue Feb 10, 2022 · 0 comments
Open

Feature Request: Flush writeInstructionsFile on change #54

bmalinconico opened this issue Feb 10, 2022 · 0 comments

Comments

@bmalinconico
Copy link

I'm using Delve through vim-test. One of the problems with that integration is that vim-test is writing it's own init file and calling tests agains that.

This means that if i run tests then change my breakpoints the new breakpoints will not be picked up until I re-run vim-test. I would like to be able to use the vim-test re-run command with new breakpoints.

While I realize this is a vim-test problem, however I think this would best be solved by adding an upstream feature to keep the command file up-to-date. That would allow vim-test to instead hook into the file provided by vim-delve.

If you are amenable to this feature I think I can handle the addition of it. Please let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant