On 12/22/2012 03:42 AM, Michael Schwendt wrote:
On Sat, 22 Dec 2012 03:15:05 +0800, Ed Greshko wrote:
> On 12/22/2012 03:11 AM, Ed Greshko wrote:
>> [egreshko@localhost ~]$ 八
>> bash: 八: command not found...
>>> True, but F18 does not do that, because there is a bug somewhere.
>>> I can reproduce it here, too.
>> What do you mean "does not do that"? What I am showing above *is* on
an F18 system.
> "After the install of PackageKit-c-n-f " got dropped....
With "F18 does not do that" I mean that a core/minimal installation of F18
prints stuff like
$ 八
bash: $'\345\205\253': command not found
$ export LC_ALL=en_GB.ISO-8859-1
$ 八
bash: $'�\205�': command not found
and it is NOT the job/task/responsibility of PackageKit-c-n-f to change
that. It is just a side-effect that PackageKit-c-n-f influences the output.
The (mis)behaviour has occured before:
https://bugzilla.redhat.com/725182
bash incorrect showing "command not found" message with non-Latin symbols
Fair enough.
In the context of my original question, nothing has changed. A "bug" exists
somewhere within bash. It may, or may not, have been patched/fixed at one time.
PackageKit-c-n-f masks the problem.
I see you've commented on the "closed" bugzilla. Don't know that it
will prompt any further action or if a new bugzilla would be appropriate.
--
Programming today is a race between software engineers striving to build bigger and better
idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far,
the Universe is winning. -- Rick Cook, The Wizardry Compiled