-
Notifications
You must be signed in to change notification settings - Fork 158
Interface addons #248
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
Open
niloct
wants to merge
7
commits into
vim-vdebug:master
Choose a base branch
from
niloct:interfaceAddons
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Interface addons #248
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When double-clicking or hitting Enter in a stack window filename, which causes it to load the file in the source window, this change makes it always center the cursor vertically.
With this commit now Vdebug places a stack sign (#>) on both Stack and Source windows, to make clear which file and line it's loading from user interface activity on Stack window. The refresh method on Runner clears both signs.
Now Vdebug can query any stack depth, and the corresponding variables and values will appear in the watch window. Also, the stack depth file and line number will also appear correctly. A visual sign (#>) was introduced to mark clearly the source and stack windows for the current stack depth and file_and_line. When the debugging resumes, these stack signs are removed from the ui. Also updated the docs with a short description of these features.
A bug in previous commit was not setting runner.context_stack_depth to zero when resuming the debugging session with a step or run command. Also the Watch window was not showing the current file and line number in the situation above.
Now a property expansion in Watch window list all children from that property. The previous behavior was listing only <pagesize> elements (i.e. based on the pagesize attribute of parent element). As before, to invoke a property expansion either double-click it or place the cursor over it and hit Enter.
The previous commit introduced the feature of getting all children from parent elements in the watchwin tree. This worked for property get UI commands issued from the Watch window itself. Now, the default context get (when hit <F11> or stepping through code or coming from Stack window) shows all children of tree depth==1. Before this commit, context get would only show <pagesize> number of children.
Works for me. 👍 |
Now the setting continuous_mode, if set, is working again: debugger starts listening on finished debugging session.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes #183, and introduces new features in Vdebug: