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

iTerm2 cursor application mode #40

Open
skriptble opened this issue Mar 28, 2016 · 2 comments · May be fixed by #166
Open

iTerm2 cursor application mode #40

skriptble opened this issue Mar 28, 2016 · 2 comments · May be fixed by #166

Comments

@skriptble
Copy link

When using iTerm2, the arrow keys are generating escape O sequences which are being printed out to screen instead of scrolling back in history of moving between characters. Is there any intention of supporting the escape O sequences in addition to the escape [ sequences?

For reference, the iTerm FAQ talks about the escape sequences under "Why my arrow/HOME/END keys are not working?"

@chzyer
Copy link
Owner

chzyer commented Mar 29, 2016

That's strange. I'm using iTerm2 too, and my arrow keys is working as expected (not the ESC O sequences), also <fn-Left>/<fn-Right> are work.
But I'm using macbook which the HOME/END keys is missing. Would you mind to provide sequences for those keys? BTW, What's your $TERM?

@skriptble
Copy link
Author

Home is OH and End is OF. $TERM is xterm-256.

I did a little more thorough testing as well since I was using the iterm2 nightly. In both Terminal and iTerm 2 (not the beta or nightly) I'm experiencing the same behavior. I've also tried on two different Macs with the same result. From what I found online, some people who've had older version of iTerm have preferences carried over that override the default behavior of iTerm2's arrow keys as well.

@lambdalisue lambdalisue linked a pull request Feb 8, 2019 that will close this issue
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

Successfully merging a pull request may close this issue.

2 participants