fix: make buffer command compatible with Windows paths (#1350)

[bwpge]

This is an incredibly boring PR. It adds a space to the b[uffer] command so that buffer names that use absolute Windows paths can be used without causing errors. This is in line with usage described in :h :buffer and :h {bufname}.

I've manually tested this change on Windows and WSL with the following types of buffers to ensure no regressions as best I can:

• No name buffers
• Buffer names with no spaces
• Buffer names with spaces in the path but not filename
• Buffer names with spaces in the filename but not path
• Buffer names with spaces in both path and filename

All cases result in the correct behavior: a warning is issued and the unsaved buffer is focused, without causing errors. Unfortunately I don't have a macOS machine handy to test but I imagine paths and buffer names behave the same or nearly the same as on WSL.

PS: The current implementation of swapping to a buffer by name may be problematic for buffer names that are numbers (see: :h :buffer). This is outside the scope of this PR, but for reference this comes from the utils.get_opened_buffers function:

neo-tree.nvim/lua/neo-tree/utils/init.lua

Lines 314 to 331 in cfe1920

	---Gets a lookup of all open buffers keyed by path with additional information
	---@return table opened_buffers { [buffer_name] = { modified = bool } }
	M.get_opened_buffers = function()
	local opened_buffers = {}
	for _, buffer in ipairs(vim.api.nvim_list_bufs()) do
	if vim.fn.buflisted(buffer) ~= 0 then
	local buffer_name = vim.api.nvim_buf_get_name(buffer)
	if buffer_name == nil or buffer_name == "" then
	buffer_name = "[No Name]#" .. buffer
	end
	opened_buffers[buffer_name] = {
	["modified"] = vim.api.nvim_buf_get_option(buffer, "modified"),
	["loaded"] = vim.api.nvim_buf_is_loaded(buffer),
	}
	end
	end
	return opened_buffers
	end

[cseickel]

This is an incredibly boring PR.

I love boring. Boring is good. Thanks for the fix!

[bwpge]

Happy to help, and sorry for goofing up the commit message style (thought I was supposed to add my issue number in parens).

Thanks for the quick merge!