Sean Dewar d85f180f26 vim-patch:9.1.0049: Make "[Command Line]" a special buffer name ... Problem: E95 is possible if a buffer called "[Command Line]" already exists when opening the cmdwin. This can also happen if the cmdwin's buffer could not be deleted when closing. Solution: Un-name the cmdwin buffer, and give it a special name instead, similar to what's done for quickfix buffers and for unnamed prompt and scratch buffers. As a result, BufFilePre/Post are no longer fired when opening the cmdwin. Add a "command" key to the dictionary returned by getbufinfo() to differentiate the cmdwin buffer instead. (Sean Dewar) Cherry-pick test_normal changes from v9.0.0954. 1fb4103206		2024-01-28 12:29:42 +00:00
..
autoload	vim-patch:a262d3f41bc5	2024-01-24 23:23:23 +01:00
colors	fix(runtime): update 'vim' color scheme to use new tree-sitter groups	2024-01-25 18:19:15 +01:00
compiler
doc	vim-patch:9.1.0049: Make "[Command Line]" a special buffer name	2024-01-28 12:29:42 +00:00
ftplugin	vim-patch:772f8f542513	2024-01-27 12:02:59 +01:00
indent
keymap
lua	vim-patch:9.1.0049: Make "[Command Line]" a special buffer name	2024-01-28 12:29:42 +00:00
macros
pack/dist/opt
plugin	fix(osc52): do not use 'vim.iter' (#27218)	2024-01-26 12:06:13 -06:00
queries
spell
syntax	vim-patch:0cc6108fea21	2024-01-27 19:38:05 +01:00
tools
tutor
CMakeLists.txt	build: various build improvements	2024-01-24 12:41:09 +01:00
delmenu.vim
filetype.lua
ftoff.vim
ftplugin.vim
ftplugof.vim
indent.vim
indoff.vim
macmap.vim
makemenu.vim
menu.vim
mswin.vim
neovim.ico
nvim.appdata.xml
nvim.desktop
nvim.png
optwin.vim
synmenu.vim