如何解决Neovim编译运行C++文件时自动填入默认输入值1的问题

Hey there! Sorry to hear you're stuck with this odd auto-input issue—having a random "1" pop up without you typing it is definitely frustrating. Let's walk through some common causes and fixes to get this sorted:

1. Inspect Your Run/Compile Configuration #

Most likely, the issue is tied to how you're launching your C++ program from Neovim:

• If you're using a custom Lua/Vimscript function or keybinding to compile and run, check for any hardcoded input. For example, a line like vim.cmd("!g++ % -o %< && echo 1 | ./%<") would pipe "1" directly into your program's stdin automatically.
• If you're relying on plugins like vim-test or toggleterm, double-check their settings. Some plugins let you define default input parameters that might be set to "1" without realizing.

2. Rule Out Terminal Buffer Autocmds or Quirks #

Neovim's built-in terminal can sometimes have unexpected behavior from auto-commands:

• Check your init file (init.lua or init.vim) for any autocmd TermOpen directives that use feedkeys() to send characters. A line like autocmd TermOpen * call feedkeys("1") would inject "1" every time a terminal buffer opens.
• Test running your compiled program directly in your system terminal (outside Neovim). If the "1" doesn't appear here, you know the problem is isolated to Neovim's config or plugins.

3. Debug Step-by-Step #

Narrow down where the issue is coming from with these quick tests:

1. First, compile your file manually in Neovim's command line: :!g++ your_file.cpp -o output
2. Then run the compiled binary without any extra flags: :!./output
   • If the "1" doesn't show up now, the problem is in your combined compile-run command or plugin setup.
3. Try a minimal Neovim config: Rename your current init.lua/init.vim temporarily, launch Neovim with default settings, and run your program. If the issue goes away, you've got a plugin or config line causing the conflict.

4. Check Build Scripts for Stdin Redirection #

If you're using Makefiles, CMake, or other build systems, verify that none of your build rules are redirecting stdin from a file that contains just the character "1". For example, a Makefile line like run: ./output < input.txt where input.txt has "1" would cause this behavior.

Start with the terminal test first—it's the fastest way to tell if this is a Neovim-specific problem or something with your build setup. Let me know if any of these steps lead you to the root cause!

内容的提问来源于stack exchange，提问作者Shivesh