-
Notifications
You must be signed in to change notification settings - Fork 47
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
Cannot navigate with arrows in terminal on macOS #3
Comments
Looks like OSX does not ship with the lesskey option for less. Following this post, I ran
Now I do not get either error stated above, but I still cannot navigate commits with arrow keys, and tab expands and overwrites the existing window instead of expanding below the prompt. |
Hey Kevin, thanks for reporting the issues. Concerning the For the arrow keys problem, I need your help here. Can you tell me which term are you using ? (echo $TERM). |
|
Hmm, not sure why it's not working. Can you update the script you installed with the latest version and try to use |
I had the same issue, and applied the less fix. And I confirm that arrow keys do not work, but j and k keys work. Cheers |
Issue resolved with Bash 4.3 or > |
Installed git-hlog by copying the script to /usr/local/bin and
chmod u+x
on it.The command works,
Navigated to a folder with a git repo with history, typed:
git hlog -d 10
It shows me commits from the last 10 days. However, there is a warning at the top of the output:
/usr/local/bin/git-hlog: line 134: lesskey: command not found
I cannot navigate down the commits with the arrow keys whatsoever. On top of that, hitting
tab
expands the commit but overlaps everything in the window (zsh or bash exhibit the same behavior in the vanilla Terminal app on mac).Quitting out prints this to terminal:
rm: /Users/kevinquillen/.lsh_less_keys_tmp: No such file or directory
Doing
which lesskey
results inlesskey not found
which is likely why this isn't working for me at the moment.Looks like a great tool otherwise and would love to get this working!
The text was updated successfully, but these errors were encountered: