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.

Sign up for GitHub

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

Jump to bottom

reason to have different names for binding method and command #65

Open
neohunter opened this issue Nov 6, 2015 · 1 comment
Open

reason to have different names for binding method and command #65

neohunter opened this issue Nov 6, 2015 · 1 comment

Comments

@neohunter
Copy link

Why you decided to have

binding.remote_pry as method to call debugger

and pry-remote to connect to it from shell

instead of have remote_pry as shell command?

What is more important that consistency?
@oystersauce8
Copy link

this drives me nuts too :)

On Fri, Nov 6, 2015 at 10:53 AM, Arnold Roa [email protected]
wrote:

Why you decided to have

binding.remote_pry as method to call debugger

and pry-remote to connect to it from shell

instead of have remote_pry as shell command?

What is more important that consistency?

—
Reply to this email directly or view it on GitHub
#65.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@neohunter @oystersauce8