From 576ce5f9f579067702be4999c3a2c62ba2ca6fdc Mon Sep 17 00:00:00 2001 From: Fabian Homborg Date: Sun, 6 Sep 2020 13:50:38 +0200 Subject: [PATCH] Remove __fish_command_not_found_handler This could lead to an infinite loop (well, stack overflow) because fish_command_not_found would also be defined to call __fish_command_not_found_handler. Since this is for - missing command errors - when downgrading we can just remove it. --- share/functions/__fish_config_interactive.fish | 5 ----- 1 file changed, 5 deletions(-) diff --git a/share/functions/__fish_config_interactive.fish b/share/functions/__fish_config_interactive.fish index 137fa9369..c12fe6c61 100644 --- a/share/functions/__fish_config_interactive.fish +++ b/share/functions/__fish_config_interactive.fish @@ -258,11 +258,6 @@ function __fish_config_interactive -d "Initializations that should be performed __update_cwd_osc # Run once because we might have already inherited a PWD from an old tab end - # For backwards-compatibility - the event doesn't exist anymore so it's harmless. - function __fish_command_not_found_handler --on-event fish_command_not_found - fish_command_not_found $argv - end - # Bump this whenever some code below needs to run once when upgrading to a new version. # The universal variable __fish_initialized is initialized in share/config.fish. set __fish_initialized 3100