On 12/21/2012 07:38 PM, Michael Schwendt wrote:
On Fri, 21 Dec 2012 19:26:47 +0800, Ed Greshko wrote:
> On 12/21/2012 06:51 PM, Michael Schwendt wrote:
>> On Fri, 21 Dec 2012 09:44:50 +0800, Ed Greshko wrote:
>>
>>> I've not run into this before....so I'm baffled.
>>>
>>> On my F17 system I get this, and it is what I expect.
>>>
>>> [egreshko@meimei ~]$ 八
>>> bash: 八: command not found...
>>>
>>> However, on my F18 test VM I get this.
>>>
>>> [egreshko@localhost ~]$ 八
>>> bash: $'\345\205\253': command not found
>>>
>>> Which is, of course, the Unicode value for 八.
>>>
>>> What has changed in a default install for that to happen? And what needs to
be changed? locale is the same on both systems.
>>>
>> Is "PackageKit-command-not-found" installed?
> It was not installed....
> Installing it "corrected" the problem.
That's the wrong conclusion. ;-)
It's an optional extension to search for missing commands in remote
repositories (via PackageKit). Many users uninstall it because it
has caused side-effects, such as delays or altered messages or it
fails always because the default search time limit is too low.
If the problem is not reproducible with PackageKit-c-n-f installed,
the problem is _not in that_ package.
I suppose I don't quite understand your meaning.....
There is no command "八" on the system. So, just like
[egreshko@localhost ~]$ adsfadsf
bash: adsfadsf: command not found...
Returns the actual "command name" as typed, I expect.
[egreshko@localhost ~]$ 八
bash: 八: command not found...
With PackageKit-c-n-f installed that is what I get....
With PackageKit-c-n-f removed I get....
[egreshko@localhost ~]$ 八
bash: $'\345\205\253': command not found
So, installing it gives me what I expect/want. Therefore, I can't see why my
conclusion is wrong.
--
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