[vim/vim] Regression after 682f630a4: the TUI can get stuck if glob() is invoked in VimEnter (Issue #19822)

Dmytro Meleshko

unread,

Mar 25, 2026, 11:42:06 AM (19 hours ago) Mar 25

to vim/vim, Subscribed

dmitmel created an issue (vim/vim#19822)

Steps to reproduce

I have an autocommand in my vimrc that checks if all plugins are installed, which uses the following code to list the plugins directory:

for subdir in glob(fnameescape(plugins_dir) . '/{,.}*/', 1, 1)

I use the glob() function with this pattern to remain compatible with older versions of Vim that might not have readdir(). However, I noticed after recent updates that when opening Vim from the terminal (Kitty), it would draw a blank screen and wait for a key to be pressed, and draw the UI only after that. This behavior can be reproduced with just this command in the vimrc:

autocmd VimEnter * eval glob('/{,.}*/')

I also noticed that while waiting for any input, Vim also leaves a child zombie bash process, so this bug probably has to do with the fact that the editor has to spawn the shell to expand the braces in the pattern.

Expected behaviour

The editor opens as normal and doesn't get stuck waiting for input.

Version of Vim

9.2.0106, but bisected the bug to 9.1.2092

Environment

Operating system: NixOS
Terminal: xterm-kitty
Shell: Zsh

Logs and stack traces

N/A

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Mar 25, 2026, 12:00:36 PM (19 hours ago) Mar 25

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#19822)

try setting set t_RF= t_RB= to disable requesting the colors

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.

Dmytro Meleshko

unread,

Mar 25, 2026, 12:05:14 PM (19 hours ago) Mar 25

to vim/vim, Subscribed

dmitmel left a comment (vim/vim#19822)

Sure enough, that fixes the symptom of the bug, I just think this problem is indicative of a mistake hidden deeper in the code of f_glob() or something like that.

—
Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

Mar 25, 2026, 12:19:47 PM (18 hours ago) Mar 25

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#19822)

Well, it might be, that your glob just receives the terminal response codes which causes this issue, that might be highly timing dependent however