Opened 18 years ago
Last modified 18 years ago
#928 closed bug
'which' aborts or kills terminal — at Version 2
| Reported by: | engima | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Applications/Terminal | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | bonefish | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description (last modified by )
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.
Change History (3)
by , 18 years ago
comment:1 by , 18 years ago
| Owner: | changed from to |
|---|
I don't know why this was assigned to me, anyway, could be either a problem with the tty layer or with pipes, and in both cases, Axel would know better :)
comment:2 by , 18 years ago
| Description: | modified (diff) |
|---|
Who is responsible for the Terminal? Currently, the component owner is "jackburton". That's why it got assigned to you.
Screenshot of error message from 'which asdf'