allow `unmap <Escape>`
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Since #2305, it is possible to map <c-c> exitMode, so one does not have to use <Escape> to exit insert mode. Now, could we regain native functionality by unmap <Escape>?
I use <Escape> very often for its native behavior in many websites, so something like <c-]><Escape> is not an acceptable option.
Thanks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no file or test; start by reviewing the key-mapping changes from #2305 and locating how map and unmap commands are handled. Confirm that unmapping restores its native behavior without removing the existing way to exit insert mode, then add or update coverage for that behavior if the mapping tests are found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100