Re: cut -d fails when using a multi-byte delimiter

[Kamil Dudka]

On Wednesday, March 27, 2019 9:04:06 AM CET Tim Rühsen wrote:
> Hi Eric,
> 
> I assume that you submitted your patches to this mailing list

See the big thread with subject "Multibyte support for sort, uniq, join, tr, 
cut, paste, expand, unexpand, fmt, fold, and pr" on this mailing list.

> as described in [1] ? That's basically 'git format-patch' output.

I do not think there was any problem with format of the submission.  As I 
understand it, the effort is now stalled because the lack of competent and 
motivated enough reviewers.

Kamil

> At least one of the maintainers should have give you some feedback...
> 
> Regards, Tim
> 
> On 3/26/19 11:02 PM, Eric Fischer wrote:
> > I fixed this in
> > https://github.com/ericfischer/coreutils/commit/093e08f91318889d7159fa8ce6
> > afa74650b66ea3 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