** Also affects: command-not-found (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: command-not-found (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: command-not-found (Ubuntu Bionic)
Importance: Undecided
Status: New
** Description changed:
+ [Impact]
+ In zsh, typing a command that is unknown to command-not-found does not
trigger a command not found message, but does nothing. If your command were
silent, you might think it was executed.
+
+ [Test case]
+
+ Type a command in zsh that command-not-found does not know about, and
+ check there is an error message that says command not found.
+
+ [Regression potential]
+
+ Given that this only affects a cnf handler, any regressions that could
+ arise would be confined to that.
+
+ There should not be any regressions, as anything that would regress now
+ should have also regressed when zsh itself changed behavior and caused
+ this bug.
+
+ [Original bug report]
+
- Using latest Ubuntu Bionic, full updated.
- Using Zsh.
My ~/.zshrc includes the following line:
- . /etc/zsh_command_not_found
+ . /etc/zsh_command_not_found
When I type (for example):
- $ sdlkfjslkdfjkdslf
+ $ sdlkfjslkdfjkdslf
it doesn't say nothing. No error message.
If I change the line #11 of /etc/zsh_command_not_found and I remove
'--no-failure-msg' option, then it works OK:
- /usr/lib/command-not-found -- ${1+"$1"} && : (line 11, without --no-
+ /usr/lib/command-not-found -- ${1+"$1"} && : (line 11, without --no-
failure-msg option)
I think the above option should be removed from
/etc/zsh_command_not_found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766068
Title:
Using Zsh, it doesn't show an error message when command not found
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1766068/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
