Description of problem: $ .. bash: ..: command not found... Similar commands are:: '..' '.' Version-Release number of selected component (if applicable): bash-4.3.30-1.fc21.x86_64 How reproducible: 100%
Hi Zbigniew, The suggestion isn't part of the bash package, it's actually provided by PackageKit-command-not-found - reassigning.
commit 0e85001b247c2ed933e5eb028cd167a8e3e40589 Author: Richard Hughes <richard> Date: Wed Nov 26 10:58:17 2014 +0000 command-not-found: Do not attempt to run for anything prefixed with '.' Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1151185
What's the intention behind this? I mean, .. indeed isn't a command while . is the short version of the `source` builtin. I'm asking because it seems to lead to confusion: http://stackoverflow.com/questions/34309107/bash-does-not-print-any-error-msg-upon-non-existing-commands-starting-with-dot Other distros (tested on Debian and Gentoo) are also not doing so.
Intention behind the bug (initial comment) or the fix (comment #2) ?
Ah, reading the referenced thread, $ .anything now does not print *any* error (even "command not found") I'd suggest filing a separate bug for this.
(In reply to Rex Dieter from comment #5) > Ah, reading the referenced thread, > > $ .anything > > now does not print *any* error (even "command not found") Exactly! > I'd suggest filing a separate bug for this. Ok. Are you gonna do it? Or should I do?
hoping you would, you're the one interested
(In reply to Rex Dieter from comment #7) > hoping you would, you're the one interested Ok
Created https://bugzilla.redhat.com/show_bug.cgi?id=1292531