[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cut -d fails when using a multi-byte delimiter
From: |
Eric Fischer |
Subject: |
Re: cut -d fails when using a multi-byte delimiter |
Date: |
Tue, 26 Mar 2019 15:02:42 -0700 |
I fixed this in
https://github.com/ericfischer/coreutils/commit/093e08f91318889d7159fa8ce6afa74650b66ea3
but
it and the rest of my multibyte fixes have been sitting unmerged for a year.
Eric
On Tue, Mar 26, 2019 at 7:23 AM Tim Rühsen <address@hidden> wrote:
> Hi,
>
> was just trying to "grep saved *.log|cut -d‘ -f2" on a wget log file and
> get
>
> cut: the delimiter must be a single character
> Try 'cut --help' for more information.
>
> Well, I am in a en_US.UTF-8 locale and that ‘ is a single character for
> me (but of course not a single byte).
>
> $ echo -n ‘|od -t x1
> 0000000 e2 80 98
>
>
> As a work-around i can use awk, but cut is just so cute and handy :-)
>
> Are there any plans to implement multi-byte support for -d ?
>
> Regards, Tim
>
>
- cut -d fails when using a multi-byte delimiter, Tim Rühsen, 2019/03/26
- Re: cut -d fails when using a multi-byte delimiter,
Eric Fischer <=
- Re: cut -d fails when using a multi-byte delimiter, Tim Rühsen, 2019/03/27
- Re: cut -d fails when using a multi-byte delimiter, Kamil Dudka, 2019/03/27
- Re: cut -d fails when using a multi-byte delimiter, Assaf Gordon, 2019/03/27
- Re: cut -d fails when using a multi-byte delimiter, Assaf Gordon, 2019/03/27
- Re: cut -d fails when using a multi-byte delimiter, Kamil Dudka, 2019/03/28
- Re: cut -d fails when using a multi-byte delimiter, Bernhard Voelker, 2019/03/28