-
Notifications
You must be signed in to change notification settings - Fork 107
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
Return and quit commands #49
Comments
Sure. Quit is really easy, so I've already added it. Return shouldn't be much harder, and is also useful. |
Return from current function: what should the command be called? @glycerine says that it is "fin" in gdb. pdb calls this "return". pdb also has "up" and "down" commands that let you move up and down the stack, so that "up" and then "next" does almost the same thing as "return". Thoughts? I think I prefer pdb's scheme. |
I would name it "return" because it's self-documenting, and on the off-chance this is ever localized, it doesn't make sense to use a French word where English is used everywhere else. It's been a while since I used pdb, but I thought up and down let you examine other stack frames, but didn't affect execution? |
Right, up and down don't affect execution, which is cool. I mentioned them because "up" followed by "next" is similar to "return". I prefer "return", too. @glycerine, does that sound good to you? |
@jeremyschlatter I don't mind 'return' -- as long as the short to type abbreviation 'r' also suffices to the same effect! |
@glycerine Of course :) |
Any plans for these?
The text was updated successfully, but these errors were encountered: