-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
add filename completion to pdb #58418
Comments
This would be extra nice because I would not have to fill in the entire path manually when I'm setting a b(reak). |
I agree. It should not be too hard to add complete_break() and other similar methods that do this to Pdb. |
Here's a patch for 3.3, adding completion to most commands (either completes locations, breakpoint numbers or expressions). Please test! |
Thanks for the work. I see that completion now works for user-defined variables, but:
|
Right, that needs to be added for every shortcut.
Indeed. That should be fixed with this new version of the patch. |
Works much better, but there are still some issues:
|
That has nothing to do with the completion.
Since break doesn't accept "~", I don't see why it should complete it. Keep in mind it's not a shell :) |
If I give it an absolute path it works, hence the complaint.
Fair enough. Perhaps the completion should not be when encountering |
But that has to do with how relative paths are handled, not with how they are entered: they are taken relative to sys.path[0]. I don't know why, and if that is the useful thing to do, but it's for another issue. >>> * using "~/" to try to complete the HOME directory doesn't work... it completes the root directory
>> Since break doesn't accept "~", I don't see why it should complete it. Keep in mind it's not a shell :)
> Fair enough. Perhaps the completion should not be when encountering
that character? That should be easy to do, yes. |
Perhaps refuse to complete all relative paths as well? |
Nope, don't think so. They are accepted and handled (albeit strangely) after all. |
New changeset 01a25f638c83 by Georg Brandl in branch 'default': |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: