-
-
Notifications
You must be signed in to change notification settings - Fork 28
Pager isn't working #68
Comments
@scottjacobsen Could you help me a little bit by running this check on your terminal emulator:
Does it works as expected, or the behavior is the same? If it's still broken, could you give me the output of less --version in your terminal emulator? |
Thanks.
Yes, this works.
It is starting to look like it could be a gem conflict. I just made a
little test script with no dependencies and Jard is working as expected
there as well.
I'll start commenting gems out of my main project and see if I can track it
down.
|
Ahhh. Glad to hear that. Yes, Ruby Jard will conflict with gems which depend on Pry or Byebug, or gems which override Readline. I discovered some of them. You can check the list in https://rubyjard.org/docs/#conflicts |
Same problem here, awaiting @scottjacobsen before trying again :-) |
Be warned - there are so many gems in my rails project, I'm not sure when
or if I'll get a chance to narrow it down :)
|
@scottjacobsen I'm waiting ;-) (joking of course) |
@scottjacobsen If your Gemfile is not sensitive, you can post it here. So that I can have a look, and find the troublesome one for you 😄 |
@scottjacobsen do you use spring ? same problem here when use jard with spring, all the keys just echoed to the screen in the pager |
When I view a variable in the REPL that doesn't fit on one screen it appears to display the attributes using
less
, and I have the:
prompt at the bottom of the screen. But theless
key bindings don't work. I've tried the vim style bindings, emacs style, typedspace
to page down, and typedq
to exit the pager. All the keys are just echoed to the screen but they do not actually do anything. It appears they are simply not passed through to the pager. All I can do isctl-c
to exit jard and start over.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Standard pager movement should work.
Environment (please complete the following information):
tput colors
in your terminal=> 256
echo $TERM
in your terminal=> xterm-256color
stty
=> No
The text was updated successfully, but these errors were encountered: