Timeline for Extract data from a file and place in different files based on one column value
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 11, 2014 at 16:52 | comment | added | X Tian | @user3116123 grep needs to handle regular expressions, do you have egrep ? | |
| Feb 11, 2014 at 15:44 | comment | added | user3116123 | receiving below error grep: illegal option -- e Usage: grep -hblcnsviw pattern file . . . | |
| Feb 11, 2014 at 15:41 | comment | added | user3116123 | what to do if | character is used instead of , . | |
| Feb 7, 2014 at 18:19 | history | edited | X Tian | CC BY-SA 3.0 | Added more rigid regex, due to comments. |
| Feb 7, 2014 at 17:01 | comment | added | terdon♦ | Sorry, I gave bad examples but the .* can also match commas so you don't know which field you're matching. Could be the second, could also be the 45th. My second complaint was wrong, you're right that the commas protect from matching foo577bar. | |
| Feb 7, 2014 at 16:59 | review | Low quality posts | |||
| Feb 7, 2014 at 17:00 | |||||
| Feb 7, 2014 at 16:58 | comment | added | X Tian | I thought my commas would make it field position dependent ? | |
| Feb 7, 2014 at 16:50 | comment | added | terdon♦ | That will match even if 577 is on another field, not the second or if it is a part of a field. For example foo577bar or yp9012,132,8,577. | |
| Feb 7, 2014 at 16:43 | history | answered | X Tian | CC BY-SA 3.0 |