Open chrisgrieser opened 1 year ago
Hey, thanks for the report. You're right and I can replicate this at the commit and also on master/neovim nightly as well.
I don't really have any clue as to why that's happening though. Opening foobar.zsh
using telescope in normal mode doesn't cause the issue despite the binds being essentially identical besides the mode.
yeah, it also puzzled me how a keymap-refactor-commit could have such an effect. could this commit maybe be reverted for the time being?
In case anyone comes finds this via search, using noice.nvim somehow suppresses the press-enter-prompt. apart from pinning a commit, this is the only workaround I have found so far for this bug
Description
Opening a zsh file (either identified via shebang, or via
.zsh
extension) via telescope results in something like an empty echo message, as if:echo ""<CR>
was run. This is noticeable when usingcmdheight=0
, where opening any zsh file now results in the need to press enter an additional time. It does not matter which picker is used, the issue occurs as long as a zsh file is opened via Telescope.I did not notice the issue with any other filetype, and it does not occur when opening zsh files with any other method.
With some bisecting, I could pin down that commit 991d5db introduced the issue; earlier commits do not have that issue. However, the commit is concerned with keymaps, and I could not figure out what exactly in that commit is affecting zsh files specifically.
Neovim version
Operating system and version
macOS 13.4.1
Telescope version / branch / rev
occurs since
991d5db
checkhealth telescope
Steps to reproduce
nvim -nu minimal.lua
foobar.zsh
in the same directorycmdheight=0
to theminimal.lua
(strictly speaking, this is not needed, it makes the bug more apparent. Otherwise, the bug is only noticeable by an empty line when running:messages
):Telescope fd
→ openfoobar.zsh
Expected behavior
No need to press enter after opening zsh files
Actual behavior
Need to press enter after opening zsh files
Minimal config