bug#41920: sort: bug report/feature request: warn is -t is effectively a no-op?

2020-06-17 Thread Eric Blake
On 6/17/20 7:22 AM, Jacek Wielemborek wrote: Hi! First of all, thanks for maintaining GNU sort! I use it very often and love its performance. Today I spent some time debugging and realized that my bug was caused by a wrong GNU invocation ("sort -k1,1 -t," instead of "sort -t, -k1,1"). Could sor

bug#41920: sort: bug report/feature request: warn is -t is effectively a no-op?

2020-06-17 Thread Jacek Wielemborek
Hi! First of all, thanks for maintaining GNU sort! I use it very often and love its performance. Today I spent some time debugging and realized that my bug was caused by a wrong GNU invocation ("sort -k1,1 -t," instead of "sort -t, -k1,1"). Could sort warn when -t is effectively a no-op because i