Call "fish_command_not_found" if a command wasn't found
Previously, when a command wasn't found, fish would emit the
"fish_command_not_found" *event*.
This was annoying as it was hard to override (the code ended up
checking for a function called `__fish_command_not_found_handler`
anyway!), the setup was ugly,
and it's useless - there is no use case for multiple command-not-found handlers.
Instead, let's just call a function `fish_command_not_found` if it
exists, or print the default message otherwise.
The event is completely removed, but because a missing event is not an error
(MEISNAE in C++-speak) this isn't an issue.
Note that, for backwards-compatibility, we still keep the default
handler function around even tho the new one is hard-coded in C++.
Also, if we detect a previous handler, the new handler just calls it.
This way, the backwards-compatible way to install a custom handler is:
```fish
function __fish_command_not_found_handler --on-event fish_command_not_found
# do a little dance, make a little love, get down tonight
end
```
and the new hotness is
```fish
function fish_command_not_found
# do the thing
end
```
Fixes #7293.
2020-08-30 03:54:13 +08:00
|
|
|
### Command-not-found handlers
|
|
|
|
# This can be overridden by defining a new fish_command_not_found function
|
|
|
|
|
|
|
|
# Read the OS/Distro from /etc/os-release.
|
|
|
|
# This has a "ID=" line that defines the exact distribution,
|
|
|
|
# and an "ID_LIKE=" line that defines what it is derived from or otherwise like.
|
|
|
|
# For our purposes, we use both.
|
|
|
|
set -l os
|
|
|
|
if test -r /etc/os-release
|
|
|
|
set os (string match -r '^ID(?:_LIKE)?\s*=.*' < /etc/os-release | \
|
|
|
|
string replace -r '^ID(?:_LIKE)?\s*=(.*)' '$1' | string trim -c '\'"' | string split " ")
|
|
|
|
end
|
|
|
|
|
2021-04-11 19:13:12 +08:00
|
|
|
function __fish_default_command_not_found_handler
|
|
|
|
printf "fish: Unknown command: %s\n" (string escape -- $argv[1]) >&2
|
|
|
|
end
|
|
|
|
|
Call "fish_command_not_found" if a command wasn't found
Previously, when a command wasn't found, fish would emit the
"fish_command_not_found" *event*.
This was annoying as it was hard to override (the code ended up
checking for a function called `__fish_command_not_found_handler`
anyway!), the setup was ugly,
and it's useless - there is no use case for multiple command-not-found handlers.
Instead, let's just call a function `fish_command_not_found` if it
exists, or print the default message otherwise.
The event is completely removed, but because a missing event is not an error
(MEISNAE in C++-speak) this isn't an issue.
Note that, for backwards-compatibility, we still keep the default
handler function around even tho the new one is hard-coded in C++.
Also, if we detect a previous handler, the new handler just calls it.
This way, the backwards-compatible way to install a custom handler is:
```fish
function __fish_command_not_found_handler --on-event fish_command_not_found
# do a little dance, make a little love, get down tonight
end
```
and the new hotness is
```fish
function fish_command_not_found
# do the thing
end
```
Fixes #7293.
2020-08-30 03:54:13 +08:00
|
|
|
# If an old handler already exists, defer to that.
|
|
|
|
if functions -q __fish_command_not_found_handler
|
|
|
|
function fish_command_not_found
|
|
|
|
# The fish_command_not_found event was removed in fish 3.2.0,
|
|
|
|
# and future versions of fish will just call a function called "fish_command_not_found".
|
|
|
|
# You have defined a custom handler, we suggest renaming it to "fish_command_not_found".
|
|
|
|
__fish_command_not_found_handler $argv
|
|
|
|
end
|
|
|
|
# First check if we are on OpenSUSE since SUSE's handler has no options
|
|
|
|
# but the same name and path as Ubuntu's.
|
|
|
|
else if contains -- suse $os || contains -- sles $os && type -q command-not-found
|
|
|
|
function fish_command_not_found
|
2020-09-05 14:41:11 +08:00
|
|
|
command-not-found $argv[1]
|
Call "fish_command_not_found" if a command wasn't found
Previously, when a command wasn't found, fish would emit the
"fish_command_not_found" *event*.
This was annoying as it was hard to override (the code ended up
checking for a function called `__fish_command_not_found_handler`
anyway!), the setup was ugly,
and it's useless - there is no use case for multiple command-not-found handlers.
Instead, let's just call a function `fish_command_not_found` if it
exists, or print the default message otherwise.
The event is completely removed, but because a missing event is not an error
(MEISNAE in C++-speak) this isn't an issue.
Note that, for backwards-compatibility, we still keep the default
handler function around even tho the new one is hard-coded in C++.
Also, if we detect a previous handler, the new handler just calls it.
This way, the backwards-compatible way to install a custom handler is:
```fish
function __fish_command_not_found_handler --on-event fish_command_not_found
# do a little dance, make a little love, get down tonight
end
```
and the new hotness is
```fish
function fish_command_not_found
# do the thing
end
```
Fixes #7293.
2020-08-30 03:54:13 +08:00
|
|
|
end
|
|
|
|
# Check for Fedora's handler
|
|
|
|
else if test -f /usr/libexec/pk-command-not-found
|
|
|
|
function fish_command_not_found
|
2021-12-28 12:56:31 +08:00
|
|
|
/usr/libexec/pk-command-not-found $argv
|
Call "fish_command_not_found" if a command wasn't found
Previously, when a command wasn't found, fish would emit the
"fish_command_not_found" *event*.
This was annoying as it was hard to override (the code ended up
checking for a function called `__fish_command_not_found_handler`
anyway!), the setup was ugly,
and it's useless - there is no use case for multiple command-not-found handlers.
Instead, let's just call a function `fish_command_not_found` if it
exists, or print the default message otherwise.
The event is completely removed, but because a missing event is not an error
(MEISNAE in C++-speak) this isn't an issue.
Note that, for backwards-compatibility, we still keep the default
handler function around even tho the new one is hard-coded in C++.
Also, if we detect a previous handler, the new handler just calls it.
This way, the backwards-compatible way to install a custom handler is:
```fish
function __fish_command_not_found_handler --on-event fish_command_not_found
# do a little dance, make a little love, get down tonight
end
```
and the new hotness is
```fish
function fish_command_not_found
# do the thing
end
```
Fixes #7293.
2020-08-30 03:54:13 +08:00
|
|
|
end
|
|
|
|
# Check in /usr/lib, where Ubuntu places this command
|
|
|
|
else if test -f /usr/lib/command-not-found
|
|
|
|
function fish_command_not_found
|
|
|
|
/usr/lib/command-not-found -- $argv[1]
|
|
|
|
end
|
|
|
|
# Check for NixOS handler
|
|
|
|
else if test -f /run/current-system/sw/bin/command-not-found
|
|
|
|
function fish_command_not_found
|
|
|
|
/run/current-system/sw/bin/command-not-found $argv
|
|
|
|
end
|
|
|
|
# Ubuntu Feisty places this command in the regular path instead
|
|
|
|
else if type -q command-not-found
|
|
|
|
function fish_command_not_found
|
|
|
|
command-not-found -- $argv[1]
|
|
|
|
end
|
|
|
|
# pkgfile is an optional, but official, package on Arch Linux
|
|
|
|
# it ships with example handlers for bash and zsh, so we'll follow that format
|
2020-10-01 03:42:15 +08:00
|
|
|
else if type -q pkgfile
|
Call "fish_command_not_found" if a command wasn't found
Previously, when a command wasn't found, fish would emit the
"fish_command_not_found" *event*.
This was annoying as it was hard to override (the code ended up
checking for a function called `__fish_command_not_found_handler`
anyway!), the setup was ugly,
and it's useless - there is no use case for multiple command-not-found handlers.
Instead, let's just call a function `fish_command_not_found` if it
exists, or print the default message otherwise.
The event is completely removed, but because a missing event is not an error
(MEISNAE in C++-speak) this isn't an issue.
Note that, for backwards-compatibility, we still keep the default
handler function around even tho the new one is hard-coded in C++.
Also, if we detect a previous handler, the new handler just calls it.
This way, the backwards-compatible way to install a custom handler is:
```fish
function __fish_command_not_found_handler --on-event fish_command_not_found
# do a little dance, make a little love, get down tonight
end
```
and the new hotness is
```fish
function fish_command_not_found
# do the thing
end
```
Fixes #7293.
2020-08-30 03:54:13 +08:00
|
|
|
function fish_command_not_found
|
|
|
|
set -l __packages (pkgfile --binaries --verbose -- $argv[1] 2>/dev/null)
|
|
|
|
if test $status -eq 0
|
|
|
|
printf "%s may be found in the following packages:\n" "$argv[1]"
|
|
|
|
printf " %s\n" $__packages
|
|
|
|
else
|
|
|
|
__fish_default_command_not_found_handler $argv[1]
|
|
|
|
end
|
|
|
|
end
|
2021-08-02 00:40:56 +08:00
|
|
|
# pacman is too slow, see #7841.
|
|
|
|
# else if type -q pacman
|
|
|
|
# function fish_command_not_found
|
|
|
|
# set -l paths $argv[1]
|
|
|
|
# # If we've not been given an absolute path, try $PATH as the starting point,
|
|
|
|
# # otherwise pacman will try *every path*, and e.g. bash-completion
|
|
|
|
# # isn't helpful.
|
|
|
|
# string match -q '/*' -- $argv[1]; or set paths $PATH/$argv[1]
|
|
|
|
# # Pacman only prints the path, so we still need to print the error.
|
|
|
|
# __fish_default_command_not_found_handler $argv[1]
|
|
|
|
# pacman -F $paths
|
|
|
|
# end
|
2021-03-05 01:29:49 +08:00
|
|
|
else
|
|
|
|
# Use standard fish command not found handler otherwise
|
|
|
|
function fish_command_not_found --on-event fish_command_not_found
|
|
|
|
__fish_default_command_not_found_handler $argv
|
|
|
|
end
|
Call "fish_command_not_found" if a command wasn't found
Previously, when a command wasn't found, fish would emit the
"fish_command_not_found" *event*.
This was annoying as it was hard to override (the code ended up
checking for a function called `__fish_command_not_found_handler`
anyway!), the setup was ugly,
and it's useless - there is no use case for multiple command-not-found handlers.
Instead, let's just call a function `fish_command_not_found` if it
exists, or print the default message otherwise.
The event is completely removed, but because a missing event is not an error
(MEISNAE in C++-speak) this isn't an issue.
Note that, for backwards-compatibility, we still keep the default
handler function around even tho the new one is hard-coded in C++.
Also, if we detect a previous handler, the new handler just calls it.
This way, the backwards-compatible way to install a custom handler is:
```fish
function __fish_command_not_found_handler --on-event fish_command_not_found
# do a little dance, make a little love, get down tonight
end
```
and the new hotness is
```fish
function fish_command_not_found
# do the thing
end
```
Fixes #7293.
2020-08-30 03:54:13 +08:00
|
|
|
end
|