-
-
Notifications
You must be signed in to change notification settings - Fork 135
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
remove n / s / c aliases #34
Comments
Hi @banister! I was completely unaware of this. I think I never got any complaints about it since I enabled the shortcuts by default... I guess they're all reporting the issues to you. I like the shortcuts myself, but I don't use |
👍 for those being optional. The error message isn't immediately obvious either:
|
Yes, the error message is not good at all. What do you guys think about my original idea: nixme/pry-debugger#31 (comment)? Or you just prefer it's completely removed? The problem here is that people using So maybe my idea is a good compromise... Or maybe not... |
Please make it optional, because I really need it. Something like |
I'll leave this opened for a bit longer to get more opinions, and then decide. But it does look like most people want them to be optional, indeed. |
this drives me mad. especially the scary error message, which makes it seem like something is really broken. |
👍 for keeping them, even if optional |
its really annoying not to be able to change the hotkeys |
@smanolloff Feel free to work on any of the features you are requesting. My current plan regarding this particular issue is to improve the error message and also refine the command. Expressions like |
I finally removed the aliases. Next version will be a major release in order to warn users who are used to the shortcuts. |
Thank you! I came here to weigh in on this as well. I am a teacher and this has caused no end of confusion to the students (and myself, when I first wasted an hour trying to figure out what was wrong with my console when I was typing |
Can we have a file that we can require for those that are used to it? pry/shortcuts.rb:
|
👍 On Wed, Oct 22, 2014 at 4:48 PM, axos88 notifications@github.com wrote:
|
Maybe, I don't know... Are the instructions to reactivate them detailed in the README not satisfactory? |
Haven't seen that, it's totally enough for me! |
great! 👍 |
Oh my god, finally. |
Thanks for fixing this! |
This had me super confused for a while! Thanks for fixing! 😺 |
Any chance for a released version that fixes this? |
I'll try to release a new version in the next three months. In the meantime just use master! |
OMG. Thank god I found this thread. I was using c as a variable and getting the obscure error for no apparent reason. Horrific... Thanks for changing it, and the sooner the better! |
For folks hitting this issue via google. You can get the shortcuts back by adding the following to your
Taken from the README |
Please. These short-cuts are great for a pure debugger, but pry has to be a REPL as well and those single letters are very, very common scratch variables. I get a lot of confused messages from people burnt by these short-cuts.
Putting the code for defining the aliases in the README (like
pry-debugger
does) is a decent compromise, IMO :)thanks!
The text was updated successfully, but these errors were encountered: