Extra Comma at End? about columscut HOT 7 CLOSED

hmm, that seems strange to me, because that's adding a comma that's not there in the input! But if that's how gnu cut does it, then I guess it makes sense to fit in with that.

from columscut.

Oh, hang on, I misunderstood you. You're saying there shouldn't be one after eight in the 3rd line?

from columscut.

Sorry - exactly right. I wouldn't expect there to be a comma after “one eight” on the third line.

from columscut.

I've looked into this one, and I've got to say I think it's a feature not a bug! You asked for 9 fields, and you got nine fields, though the last one is a blank field because there's no matching data in the input. In fact this example:

echo 1,2,3,4 | ./ccut -d . -f 3,2,6,7

which outputs

3,2,

arguably should output:

3,2,,

from columscut.

Good point - I like it! That normalizes the input into fixed numbers of fields.

from columscut.

Okay, now I just have to make it actually do that, as the current version doesn't.

from columscut.

Okay, got this to work for release v2.10.

Pretty shocked to discover that gnu cut does this:

echo "1,2,3,4,5" | cut -d , -f 2,3,20,4,5
2,3,4,5

If you're using cut to extract fields into values (what else is it for?) you'll have the wrong things in the wrong boxes, if you see what I mean.

Anyways, gonna close this one now.

from columscut.