No-break space after typing | and command-not-found crash
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| command-not-found |
New
|
Undecided
|
Unassigned | ||
Bug Description
I can reproduce this bug with "echo 1 | wc -l".
The character after | is not space, but 0xa0. For some reason some times when I type | and space in a terminal or a text editor, it enters a no-break space (0xa0) instead of a space. On the command line or in the text editor these two spaces are indistinguishable, but a no-break space causes annoying problems.
I have seen this problem in various systems, currently in Ubuntu 12.04. Usually the command "echo 1 | wc -l" would produce an error message because " wc" command was not found. This time command-not-found crashed:
Sorry, command-not-found has crashed! Please file a bug report at:
https:/
Please include the following information with the report:
command-not-found version: 0.2.44
| Seppo Enarvi (senarvi) wrote | #1 |
I noticed today what causes the no-break space to be inserted after |. Alt+Space inserts a no-break space, so if I keep Alt down too long after inserting | and try to insert a space, it will turn into a no-break space. (This is unrelevant to the command-not-found crash.)