Hide Forgot
Warning: this merely an instance of unexpected behavior. I'm filling this for sake of completeness. Description of problem: See http://unix.stackexchange.com/questions/322000/why-does-bash-treat-commandlines-starting-with-dots-specially (I'm the author) Version-Release number of selected component (if applicable): GNU bash, version 4.3.42(1)-release (x86_64-redhat-linux-gnu) Distro's default implementation of command_not_found_handle How reproducible: Always, unless unsetting of command_not_found_handle. Steps to Reproduce: 1. Type ".whatever this is going to be ignored" into the shell (w/o quotes) 2. Hit enter. 3. Nothing happens. Actual results: Nothing happens. Expected results: bash : .whatever : command not found... Additional info: This is unexpected behavior, severity: minimal
(In reply to mareksp.92+bugs from comment #0) > How reproducible: > Always, unless unsetting of command_not_found_handle. Any idea, where is command_not_found_handle being set on your system? I have it unset by default on my Fedora 24 box and bash behaves as expected: [kdudka@f24 ~]$ .whatever this is going to be ignored bash: .whatever: command not found
So, looking where the command_not_found_handle() [bash function] comes from, I see this: > /etc/profile.d/PackageKit.sh:9:command_not_found_handle () { According to 'dnf whatprovides' this is part of: > PackageKit-command-not-found-1.1.3-2.fc24.x86_64 : Ask the user to install command line programs automatically > Repo : @System Re-assigning...
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fixed upstream 13 days ago in commit d3533878038ebdcf6ae2b3524c8c8e2f1b47e84b.
Also this is a duplicate of #1292531, as my research found out. I don't know whether to close this one or the other one.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.