[Pkg-zsh-devel] Bug#813331: command-not-found: False positives for multiple commands delimited by "; " in zsh

[Axel Beckert]

Package: command-not-found
Version: 0.2.38-1
Severity: normal
Affects: zsh

Hi,

I just run into the following issue on Sid/Experimental (zsh 5.2-3,
command-not-found 0.2.38-2), but it also seems also present in Jessie
(zsh 5.0.7-5 and command-not-found 0.2.38-1) and Wheezy (zsh 4.3.17-1
and 0.2.38-1):

→ true; false
No command 'true;' found, did you mean:
 Command 'true' from package 'coreutils' (main)
true;: command not found
→ true;false
true;false: command not found
→ true;
→

(The "true;false" example works fine if command-not-found is not
installed. And of course, coreutils is installed. :-)

This doesn't happen with bash:

$ true; false
$ true;false
$

Seems as if command-not-found -- if run under zsh -- does not split
commands at ";", just at space.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), (111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), (105, 'experimental-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages command-not-found depends on:
ii  apt-file     3.0~exp4
ii  lsb-release  9.20160110
ii  python-gdbm  2.7.11-2
pn  python:any   <none>

command-not-found recommends no packages.

command-not-found suggests no packages.

-- no debconf information