Skip to content

Neovim opens in operator pending mode on Windows #4671

@marchollinger

Description

@marchollinger

Checklist

  • I have read through the manual page (man fzf)
  • I have searched through the existing issues
  • For bug reports, I have checked if the bug is reproducible in the latest version of fzf

Output of fzf --version

0.67.0 (2ab923f)

OS

  • Linux
  • macOS
  • Windows
  • Etc.

Shell

  • bash
  • zsh
  • fish

Problem / Steps to reproduce

Environment

pwsh version: PowerShell 7.5.4
Operating system: Windows 10.0.26200
Terminal emulator: Windows Terminal Version: 1.23.20211.0
Neovim vesrion: v0.11.6

I found some weird behavior when using become:nvim {} and --height. When I run this command:

fzf --bind "enter:become:vim {}" --height='100%'

Everything works as expected. Neovim opens the selected file in normal mode.

However, if I set --height to anything other than 100%, Neovim opens in operator pending mode and behaves as if I pressed y to yank. Navigating up or down then triggers a yank instead of just moving the cursor.

Image

In the nvim cmdline, y can be seen as if I typed it in normal mode. It also outputs no previous search which is a message from leap.nvim that appears if ; is pressed without a previous search. Somehow, keystrokes are being sent to neovim after opening without me doing anything. If I use nvim --clean then the leap message is not displayed but the y keystroke is still being sent.

Does anyone know what could be causing this? This behavior only occurs in PowerShell, in zsh on Mac or WSL2 everything works fine.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions