Opened 18 years ago
Last modified 18 years ago
#928 closed bug
'which' aborts or kills terminal — at Initial Version
| Reported by: | engima | Owned by: | jackburton |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Applications/Terminal | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | bonefish | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
When running the shell command 'which' it will always result in either:
If the command we're trying to find doesn't exit, an error message that some gibberish has been terminated, and also kills the terminal (Attaching screenshot) If the command exists, we just get the terminal closed immediately
The command 'which' uses, causing the fault is 'echo $(builtin type $cmd | sed lq)'. Typing this out on the command line results in the same problem.
Note:
See TracTickets
for help on using tickets.
Screenshot of error message from 'which asdf'