GNU bug report logs - #25544
regression: Windows version grep not search two non ASCII words separated by space

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 25544 in the body.
You can then email your comments to 25544 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Михаил Гаврилов
 <mikhail.v.gavrilov <at> gmail.com>
To: bug-grep <at> gnu.org
Subject: regression: Windows version grep not search two non ASCII words
 separated by space
Date: Thu, 26 Jan 2017 16:17:42 +0500

Windows version grep not search two non ASCII words separated by space
More details described here: https://github.com/geany/geany/issues/1366
Last workable version is 2.24




--
Best Regards,
Mike Gavrilov.

Message #10 received at 25544-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Михаил Гаврилов
 <mikhail.v.gavrilov <at> gmail.com>, 25544-done <at> debbugs.gnu.org
Subject: Re: bug#25544: regression: Windows version grep not search two non
 ASCII words separated by space
Date: Fri, 27 Jan 2017 14:35:54 -0800

Михаил Гаврилов wrote:
> Windows version grep not search two non ASCII words separated by space
> More details described here: https://github.com/geany/geany/issues/1366
> Last workable version is 2.24

As this bug appears to be only in the MS-Windows port and is likely related to 
that port, please report it to whoever maintains the MS-Windows version. I'm 
going to close the bug here, as nobody that I know of is monitoring this mailing 
list and is maintaining the MS-Windows version.

Message #13 received at 25544-done <at> debbugs.gnu.org (full text, mbox):

From: mikhail <mikhail.v.gavrilov <at> gmail.com>
To: Paul Eggert <eggert <at> cs.ucla.edu>, 25544-done <at> debbugs.gnu.org
Subject: Re: bug#25544: regression: Windows version grep not search two non
 ASCII words separated by space
Date: Sat, 28 Jan 2017 19:36:27 +0500

On Fri, 2017-01-27 at 14:35 -0800, Paul Eggert wrote:
> As this bug appears to be only in the MS-Windows port and is likely
> related to 
> that port, please report it to whoever maintains the MS-Windows
> version. I'm 
> going to close the bug here, as nobody that I know of is monitoring
> this mailing 
> list and is maintaining the MS-Windows version.

Excuse me, can you help me find maintainers of Windows version? I don't
 see mailing list of grep MS-Windows version.
Sorry for inconvenience, I am thought that both versions maintained by
same developers.

Message #16 received at 25544-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: mikhail <mikhail.v.gavrilov <at> gmail.com>, 25544-done <at> debbugs.gnu.org
Subject: Re: bug#25544: regression: Windows version grep not search two non
 ASCII words separated by space
Date: Sat, 28 Jan 2017 16:32:36 -0800

mikhail wrote:
> Excuse me, can you help me find maintainers of Windows version? I don't
>  see mailing list of grep MS-Windows version

Sorry, I don't know who they are. Maybe they want to remain anonymous.

You might consider moving your application to a GNU/Linux platform instead, as 
you'll have more freedom and grep is much better supported. If it's important 
enough for you to send in bug reports, it may well be important enough for you 
to switch.

Message #19 received at 25544 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Михаил Гаврилов
 <mikhail.v.gavrilov <at> gmail.com>
Cc: 25544 <at> debbugs.gnu.org
Subject: Re: bug#25544: regression: Windows version grep not search two non
 ASCII words separated by space
Date: Sun, 29 Jan 2017 19:53:04 +0200

> From: Михаил Гаврилов
> 	<mikhail.v.gavrilov <at> gmail.com>
> Date: Thu, 26 Jan 2017 16:17:42 +0500
> 
> Windows version grep not search two non ASCII words separated by space
> More details described here: https://github.com/geany/geany/issues/1366
> Last workable version is 2.24

The detailed description indicates that the problem happens when the
Windows console output is switched to UTF-8, and therefore the file
being searched includes the Cyrillic text encoded in UTF-8.
Therefore, my crystal ball says that the root cause of this is because
Windows non-ASCII character functions from the C runtime library
cannot support UTF-8 as the multibyte encoding.

My suggestion is not to use UTF-8 on Windows in conjunction with
software ported from Posix systems, because making such ports support
UTF-8 on Windows is a very large job (in a nutshell, you need to
replace all the runtime functions with alternative versions, and if
you want support beyond the BMP, you need to use a 32-bit data type
instead of wchar_t).  In the particular case in point, I suggest to
use a single-byte codepage that supports Cyrillic letters.  Then the
problem should go away.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.