Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
eslint --init: arrow keys not working on git bash
See original GitHub issueI don’t know if this is an eslint specific issue but arrow keys when selecting a setup doesn’t seem to work on Git Bash. But when I tried it on ConEmu, it works.
Tell us about your environment
- ESLint Version: 3.11.1
- Node Version: 6.6.0
- npm Version: 4.0.3
"devDependencies": {
"eslint": "^3.11.1",
"nodemon": "^1.11.0"
}
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Can't use arrow keys in Git Bash (Windows) - Stack Overflow
Solution for me: In webstorm console everything is working correctly, after changing eslint.
Read more >eslint/eslint - Gitter
it tells me to use the arrow keys, but I keep getting the wrong options once selected ... Nvm I figured it out...
Read more >Vue-cli: arrow key not working while creating new project on ...
Coding example for the question Vue-cli: arrow key not working while creating new project on git bash windows-Vue.js.
Read more >Vue-Cli: Arrow Key Not Working While Creating New Project ...
To create a new profile run the Terminal: Select Default Profile command and For example to remove the Git Bash profile on Windows...
Read more >How to setup ESLint and Prettier on Node - SourceLevel
If you work on Windows and bash is not installed, ... Initialize an npm (Node Package Manager) project by typing the following command...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Possible workaround: Use number key then Enter to select your choice.
It looks like this is very similar to https://github.com/SBoudrias/Inquirer.js/issues/266
…which was caused by https://github.com/nodejs/node/issues/5384
…which was supposedly fixed in Node 6.2.0, so I’m not completely sure why it’s appearing in Node 6.6.0.