fix: check if window is valid before calling get_cursor

[samiulsami]

Fixes issue when toggling on/off the floating chat window quickly, which sometimes causes the program to attempt a scheduled write on an invalid window:

my config for reference:

{
	model = "gpt-5-mini",
	temperature = 0.1,
	window = {
		layout = "float",
		width = 1,
		height = 1,
		row = 9999999,
		blend = 10,
	},
	auto_insert_mode = true,
	mappings = {
		close = {
			normal = "<Esc>",
			insert = "<C-c>",
			callback = function()
				chat.save(vim.fn.sha256(vim.fn.getcwd()))
				chat.close()
			end,
		},
	},
})

vim.keymap.set({ "n", "v", "i" }, "<A-C>", function()
	chat.toggle()
end, { noremap = true, silent = true, desc = "Copilot Chat: Toggle" })

[deathbeam]

Hmm this just hides all errors from the callback completely which is not rly proper fix (as the callback is basically everything after .schedule_main). It looks like issue is completion so maybe just some additional validation there is needed?

[deathbeam]

Basically the proper fix is check if local row_changed = vim.api.nvim_win_get_cursor(win)[1] ~= row

the win is valid first

[samiulsami]

Collaborator

Basically the proper fix is check if local row_changed = vim.api.nvim_win_get_cursor(win)[1] ~= row

the win is valid first

Ah of course! updated and tested.

[deathbeam]

Thanks!

@all-contributors add @samiulsami for code

[allcontributors]

@deathbeam

I've put up a pull request to add @samiulsami! 🎉