Bug 1151185
| Summary: | Bogus help message for not found command ".." | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Zbigniew Jędrzejewski-Szmek <zbyszek> |
| Component: | PackageKit | Assignee: | Richard Hughes <rhughes> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 21 | CC: | admiller, hek2mgl, jonathan, kalevlember, ooprala, rdieter, rhughes, smparrish |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-11-26 10:58:39 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Zbigniew Jędrzejewski-Szmek
2014-10-09 18:12:54 UTC
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 |