bug-datamash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-datamash] Datamash cut in v1.5 doesn't support space in csv


From: John Rhee
Subject: Re: [Bug-datamash] Datamash cut in v1.5 doesn't support space in csv
Date: Thu, 26 Sep 2019 16:45:53 -0400

Hi Assaf, 

Thanks for the fast reply!  I should've included the example in the first place.  Btw, -t separator is not a requirement for the cut behavior I'm reporting, but rather using a header name that contains a space.


$ echo -e "Header 1\tHeader 2\tHeader 3\nData A\tData B\tData C"
Header 1 Header 2 Header 3
Data A Data B Data C

# Column HEADER NUMBER works fine
$ echo -e "Header 1\tHeader 2\tHeader 3\nData A\tData B\tData C" |datamash -H cut 2
cut(Header 2)
Data B

# Column HEADER NAME WITH SPACE does not work
$ echo -e "Header 1\tHeader 2\tHeader 3\nData A\tData B\tData C" |datamash -H cut "Header 2"
datamash: invalid operation ‘2’
$ echo -e "Header 1\tHeader 2\tHeader 3\nData A\tData B\tData C" |datamash -H cut 'Header 2'
datamash: invalid operation ‘2’
$ echo -e "Header 1\tHeader 2\tHeader 3\nData A\tData B\tData C" |datamash -H cut Header\ 2
datamash: invalid operation ‘2’
$ echo -e "Header 1\tHeader 2\tHeader 3\nData A\tData B\tData C" |datamash -H cut Header?2
datamash: invalid operand ‘?2’
$ echo -e "Header 1\tHeader 2\tHeader 3\nData A\tData B\tData C" |datamash -H cut Header.2
datamash: invalid operand ‘.2’
$ echo -e "Header 1\tHeader 2\tHeader 3\nData A\tData B\tData C" |datamash -H cut Header 2
datamash: invalid operation ‘2’


# Replace header spaces with _
$ echo -e "Header_1\tHeader_2\tHeader_3\nData A\tData B\tData C"
Header_1 Header_2 Header_3
Data A Data B Data C

# Column header name without space works fine
$ echo -e "Header_1\tHeader_2\tHeader_3\nData A\tData B\tData C" |datamash -H cut Header_2
cut(Header_2)
Data B


Thanks, 
John

On Thu, Sep 26, 2019, 1:15 PM Assaf Gordon <address@hidden> wrote:
Hello,

On 2019-09-26 10:49 a.m., John Rhee wrote:
> The new "cut" feature in v1.5 suggested by Torsten is great, but when
> using comma-separator (-t,) it doesn't seem to handle space in header
> names (I tried escape, quotes, and wildcards).  Can you please consider
> it in a future release?
>

Thanks for the feedback - can you provide a small example of the input
file that isn't working as expected (and the command-line you've used) ?

Just so I'll know to focus on the actual issue you are experiencing.

Thanks,
  - assaf




reply via email to

[Prev in Thread] Current Thread [Next in Thread]