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.

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

Jumping at the beginning or end of line with CTRL or ALT + arrows #11

Closed
jerefrer opened this issue Sep 7, 2015 · 12 comments
Closed

Jumping at the beginning or end of line with CTRL or ALT + arrows #11

jerefrer opened this issue Sep 7, 2015 · 12 comments

Comments

@jerefrer
Copy link

jerefrer commented Sep 7, 2015

Hi there,

Thank you for building on top of jazz_hands for a more to-date bundle of useful gems.

But there's one thing I lost in the transition : I can't jump to the beginning of words with CTRL or ALT + the arrow keys. I'm very used to navigate like this so it feels very annoying to me not to be able to use them ...

When I try to do for example CTRL + LEFT ARROW and then CTRL + RIGH ARROW I get 5D and 5C printed out but the cursor doesn't move, like this:

SomeClass5D5C

The thing is I don't know why it's not working anymore. Maybe you know ?

@plribeiro3000
Copy link
Owner

So jazz_fingers neither jazz_hands have anything related to this configuration.
If something stopped adding this feature it must be one of the dependencies. In the bump of the dependencies this feature might have changed or removed.

@plribeiro3000
Copy link
Owner

I could not find anything on the dependency projects that could be the culprit for such behaviour.
Can you confirm this works in jazz_hands using the same machine as you are using jazz_fingers?

@jerefrer
Copy link
Author

jerefrer commented Sep 8, 2015

I confirm it works well on jazz_hands on the same machine, same project.

By looking at the Gemfile.lock diff I think the main difference is that jazz_fingers is using byebug where jazz_hands uses debugger.

So I've looked at byebug directly and found this issue deivid-rodriguez/byebug#118. It seems it's really a byebug issue so I'll stop bothering you here ;)

Thanks for you time !

@jerefrer jerefrer closed this as completed Sep 8, 2015
@plribeiro3000
Copy link
Owner

Wow. Sorry if i missed that issue. =s
So it seems we need to check readline to fix that, huh?

@jerefrer
Copy link
Author

jerefrer commented Sep 8, 2015

I think it's related to some environments, and to the way you compile ruby. In my case I'm on Archlinux and using RVM.
I haven't managed to find the right trick for now but I'l keep trying.

@plribeiro3000
Copy link
Owner

Hmm. Thank you for the feedback.
Let me know how it goes.

Thanks!

@jerefrer
Copy link
Author

jerefrer commented Sep 8, 2015

Okay so actually I just needed to update jazz_fingers to update byebug and the issue is gone.

But now I've lost colors ... It's not my day ...

I've tried to go at full throttle but still no colors and noawesome print. Hirb works.

if defined?(JazzFingers)
  Pry.color = true
  Hirb.enable
  JazzFingers.configure do |config|
    config.colored_prompt = true
    config.awesome_print = true
    config.coolline = true
  end

  require 'jazz_fingers/setup'
end

@plribeiro3000
Copy link
Owner

Hmmm, which version of the dependencies are you using?

@jerefrer
Copy link
Author

jerefrer commented Sep 9, 2015

jazz_fingers (2.0.2)
awesome_print (1.6.1)
coolline (0.5.0)
unicode_utils (1.4.0)
pry (0.10.1)
pry-byebug (3.2.0)
pry-coolline (0.2.5)
pry-doc (0.8.0)
pry-git (0.2.3)
pry-remote (0.1.8)
hirb (0.7.3)
coderay (1.1.0)
method_source (0.8.2)
slop (3.6.0)

@jerefrer
Copy link
Author

jerefrer commented Sep 9, 2015

Well actually it's not working ... I got misled because before the upgrade rails c used to start the console through Pry and now it appears it doesn't. But if I add a binding.pry breakpoint then it properly opens Pry with colors and everything along with the readline bug ...

@plribeiro3000
Copy link
Owner

Oh yeah. i did remove pry-rails as dependency so this code works pretty well in non rails apps.
Maybe we should have this in README?

@jerefrer
Copy link
Author

Yep definitely

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants