Files
Johannes Altmanninger 6e036740de fish_command_not_found: remove legacy event handler
We no longer emit the "fish_command_not_found" event ourselves,
so the event handlers are only useful to users who
1. run "emit fish_command_not_found"
2. copy the definition of "fish_command_not_found" to their config and run
   that with fish < 3.2.

Probably no one does 1; there are no matches in
https://github.com/search?utf8=%E2%9C%93&q=%22emit+fish_command_not_found%22+language%3Afish&type=code

Reason 2 is less relevant after 5 years.

For additional evidence, none of our specializations
("/usr/libexec/pk-command-not-found" etc.)  react to the event,
and no one has ever complained.

Stop registering any fish_command_not_found as event handler,
for consistency and simplicity.

While at it, remove the documentation on how to make it work for
version < 3.2.
2026-05-11 10:24:12 +08:00
..
2025-12-18 15:04:06 +01:00
2026-01-04 13:08:26 +01:00
2025-12-08 21:19:43 +08:00
2025-12-15 19:23:01 +01:00
2025-05-28 17:09:13 +02:00
2025-01-06 19:40:30 -06:00
2026-01-04 13:08:26 +01:00