tpope / tpope/vim-eunuch

Default `<CR>` mapping breaks Nvim's `ins-completion` menu

Open Beginner friendly
#121 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Vim Script
Stars
1.9k
Forks
79
PR merge metrics
No merged PRs in 30d

Description

The default <CR> mapping added by eunuch.vim breaks Nvim's (and maybe Vim's too?) ins-completion menu.

Minimal repo:

  • Launch Nvim with an empty config
  • :packadd vim-eunuch
  • Type hello hi hey howdy, just to get ins-completion something to complete. What exactly you type doesn't matter.
  • On a new line, type h<C-P> to trigger ins-completion
  • Select an option and press <CR>.
  • The option is not selected.

https://github.com/user-attachments/assets/19c281b4-a0d1-4774-9199-fdcedd0af7a9

As a workaround, putting imap <CR> <CR> in init.vim will fix the issue, but ideally, I shouldn't need to do that.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the minimal reproduction: launch Nvim with an empty config, run :packadd vim-eunuch, trigger ins-completion with h, and press on an option. Inspect the plugin's default mapping and verify that completion selects the chosen option without requiring imap in init.vim.

Written by the indexing model from the issue text.

Assessment

Tech stack
vim
Domain
tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.