Package: command-not-found Version: 18.04.5-1 Severity: important Dear Maintainer,
The latest version of the command-not-found/zsh combination is failing silently whenever the command-not-found-handler does not match. To reproduce: $ zsh --no-rcs localhost% source /etc/zsh_command_not_found localhost% some-command-that-does-not-exist localhost% Observe that no error message is printed. I would expect the line 'command not found: some-command-that-does-not-exist' to be printed. The zsh documentation agrees with me. From http://zsh.sourceforge.net/Doc/Release/Command-Execution.html: > If the function wishes to mimic the behaviour of the shell when the command is > not found, it should print the message ‘command not found: cmd’ to standard error > and return status 127. Looking at the `command-not-found-handler` definition, it is not printing any message, not is it allowing `/usr/lib/command-not-found` to print its own message. -- System Information: Debian Release: 10.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages command-not-found depends on: ii apt-file 3.2.2 ii lsb-release 10.2019031300 ii python3 3.7.3-1 ii python3-apt 1.8.4 command-not-found recommends no packages. Versions of packages command-not-found suggests: pn snapd <none> -- no debconf information
