You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not an issue but question. As of now, csvtk sub-commands supporting the flag -n or --line-number to "print line number as the first column ("n")" are as under:
grep
filter
filter2
sample
One way to print line number as the first column at the end of workflow is as under:
Using a sub-command like grep in the manner shown above just to print line numbers is certainly inefficient. And yes, only one sub-command cat supporting -n to print line numbers will be excellent. One more thing I've noticed is that cat sub-command does not support gzipped input unlike other sub-commands. It would be nice for it to do so.
This is not an issue but question. As of now, csvtk sub-commands supporting the flag -n or --line-number to "print line number as the first column ("n")" are as under:
grep
filter
filter2
sample
One way to print line number as the first column at the end of workflow is as under:
csvtk sub-command ... |^
csvtk another-sub-command ... |^
csvtk grep -n -f1 -r -p ".*" |^
csvtk pretty
I'm wondering if there a better (more processor and RAM friendly) way to to print line numbers than using
csvtk grep -n -f1 -r -p ".*"
The text was updated successfully, but these errors were encountered: