BUG: When enabling the plugin it seems to interfere with noice.vim

[majordoobie]

When I open a python file I get this message saying that noice.vim has been overwritten it also adds =31;OK at the end of my python file when I open a file. I tried to diagnose it with some AI and this is what it says:

  The Problem:

  venv-selector's UV integration (for the uv Python package manager) has a bug where it incorrectly overwrites vim.notify with a table instead of a function. This is what caused:
  1. The "vim.notify has been overridden" error from noice.nvim
  2. The mysterious "=31;OK" text appearing in your Python files (likely terminal escape sequences being mishandled)

  From your diagnostic log (line 24-25), the UV module was running on every BufEnter for Python files and corrupting the notification system.

  The Fix:

  I've made these changes to lua/plugins/code_editing.lua:54-74:

  1. Fixed syntax error - Removed the extra } and fixed indentation
  2. Disabled UV support - Added settings = { search = { uv = { enable = false } } } to prevent the buggy UV integration from running
  3. Proper configuration structure - Maintained compatibility with venv-selector while preventing the corruption

  Next Steps:

  1. Restart Neovim or run :Lazy sync to reload the plugin with the new configuration
  2. Test by opening a Python file - you should no longer see:
    - The vim.notify warning
    - The "=31;OK" text appearing
  3. Virtual environment selection will still work with ,v, it just won't auto-detect uv-based environments

  If you do need UV support, you might want to check for updates to venv-selector.nvim or file a bug report, as this is clearly a plugin issue.

Not sure if this is valid or not, just wanted to share what it said.

My current config looks like this

	{
		"linux-cultist/venv-selector.nvim",
		dependencies = {
			"neovim/nvim-lspconfig",
			{ "nvim-telescope/telescope.nvim", branch = "0.1.x", dependencies = { "nvim-lua/plenary.nvim" } },
		},
		ft = "python", -- Load when opening Python files
		keys = {
			{ ",v", "<cmd>VenvSelect<cr>" }, -- Open picker on keymap
		},
		opts = {
			enable_default_searches = true,
			enable_cached_venvs = true,
			-- Disable UV support to prevent vim.notify corruption
			settings = {
				search = {
					uv = { enable = false },
				},
			},
		},
	},

[linux-cultist]

Hmm ok! I havent noticed this myself but I will install noice and see what happens. Thank you!

[majordoobie]

Am I still supposed to use "nvim-lspconfig"? What is your current setup?

[linux-cultist]

You can if you want but its not a requirement. Its just containing default configs for your enabled lsp servers, and if you want to override the defaults, you can.

So its not something the plugin requires. It just makes your neovim lsp config more convenient, weather you use this plugin or not.

I had my own configs for lsp servers before, but now I also use nvim-lspconfig as a default also.

[majordoobie]

I was able to fix it! Looks like vent-selector.nvim is overwriting vim.notify which noice.nvim also does. So all I did was let venv-select.nvim setup then revert back to noice.nvim

	{
		"linux-cultist/venv-selector.nvim",
		dependencies = {
			{ "nvim-telescope/telescope.nvim", branch = "0.1.x", dependencies = { "nvim-lua/plenary.nvim" } },
		},
		ft = "python", -- Load when opening Python files
		keys = {
			{ ",v", "<cmd>VenvSelect<cr>" }, -- Open picker on keymap
		},
		config = function()
			-- Store original vim.notify before venv-selector loads
			local original_notify = vim.notify

			require("venv-selector").setup({})

			-- Restore vim.notify after venv-selector setup (it overrides in init.lua)
			vim.schedule(function()
				if type(vim.notify) ~= "function" and type(original_notify) == "function" then
					vim.notify = original_notify
				end
			end)
		end,
	},

[linux-cultist]

Ok! I will look at it the coming days, see if the plugin can coexist with noice without having to do anything :)

[linux-cultist]

I moved the override code into the setup function so as long as you load venv-selector after vim.notify, things should work as expected. Please test and see!

Remember to update plugin before your test too. :)

[linux-cultist]

Did you manage to find a few minutes to see if its working now? I would appreciate it. :)

[lxymahatma]

Did you manage to find a few minutes to see if its working now? I would appreciate it. :)

I'm still having this issue with the latest versions of both noice.nvim and venv-selector.nvim. It seems that noice throws this warning whenever vim.notify is overwritten by another plugin, regardless of whether it happens before or after venv plugin setup.

Maybe we could have a boolean option in the options (e.g., notify/notify_integration = true/false) to explicitly control whether venv-selector should try to require nvim-notify so users who use noice (or other UI plugins) can explicitly disable the built-in notify dependency to prevent this issue?

[linux-cultist]

Yeah I guess thats the best option. I havent worked on the plugin for a while but will add it when I sit down with it. Thank you. :)