Timeline for Why does cut fail with bash and not zsh?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 12, 2016 at 3:48 | comment | added | lauir |
Would help a lot to see the resulting bash.sh in the answer
|
|
| Jun 10, 2016 at 20:37 | comment | added | Stéphane Chazelas | @BinaryZebra, indeed, well spotted. Glad they've fixed it. | |
| Jun 10, 2016 at 20:18 | comment | added | user79743 | @StéphaneChazelas No split (nor glob) happens on bash 4.4 | |
| Jun 10, 2016 at 18:12 | comment | added | terdon♦ | @StéphaneChazelas fair enough, the issue is with the split part anyway. | |
| Jun 10, 2016 at 17:51 | comment | added | Stéphane Chazelas |
@terdon, in <<< $line, bash does split but not glob. There's no reason it would do split here as <<< expects a single word. It splits and then joins in that case, which makes little sense and is against all other shells implementations that have supported <<< before or after bash. IMO it's a bug.
|
|
| Jun 10, 2016 at 17:43 | comment | added | terdon♦ | @user1717828 yes, it's called the spit+glob operator. It's what happens when you use a variable unquoted in bash and similar shells. | |
| Jun 10, 2016 at 16:18 | comment | added | user1717828 |
Is there any reason Bash sees a \t and replaces it with a space?
|
|
| Jun 10, 2016 at 12:05 | vote | accept | Sparhawk | ||
| Jun 10, 2016 at 11:44 | history | answered | Michael Vehrs | CC BY-SA 3.0 |