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
Breakpoint moves with copy line up/down action #75426
Comments
(Experimental duplicate detection) |
This is as designed... The copy line down action is implemented by inserting the line text above it, so that's why the breakpoint moves. We will not reimplement the action just to accommodate this case, and it is IMHO not clearly wrong... |
@alexandrudima This really doesn't seem to be as designed but rather a clear oversight, and for multiple reasons:
|
I wouldn't say that keeping the breakpoint, bookmark, or any other decoration/data in the original line is correct either, because the command is I'm not sure if copying/cutting the entire line shouldn't bring its breakpoint/bookmarks (sometimes I hoped it should). But to this, the API should be updated to describe the original IMHO, I prefer the way it works today, even with this naming conflict. The Bookmarks extension, at least, should remain this way. |
I think the copy line up/down action really should also copy all break points, bookmarks and other stuff associated to the line. Unfortunately, as far as I know, there is no generic way to (deep-) copy all the associated data. Since copying the associated data is off the table, we can still control if the original or the copy should get all the associated data. I think there are valid arguments for both the old (original) and the new (copied) line, so this is not clearly a bug, but rather the behavior is open for discussion. |
Yes, the Bookmarks extension has its own storage, and a custom sticky algorithm to update the Bookmark position (line) when the user changes the file. Technically speaking, |
Version:
Steps to Reproduce:
Bug:
The break-point moves with the copied line. It should stay.
Does this issue occur when all extensions are disabled? Yes
The text was updated successfully, but these errors were encountered: