Comment 4 for bug 218637
Revision history for this message
| crwl (crwl) wrote Re: [Hardy] Piping commands does not work always | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Are you sure you aren't inserting an altgr+space character after the pipe character instead of just the normal space? I'm suspecting this because there is an additional empty space after "bash: (somecommand): command not found"
If grep wasn't found, bash would say:
bash: grep: command not found
you are seeing:
bash: grep: command not found