From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: dired-do-find-regexp failure with latin-1 encoding Date: Sun, 29 Nov 2020 17:06:23 +0200 Message-ID: <838sakmccw.fsf@gnu.org> References: <87blfhjr4q.fsf@gmx.net> <83k0u5mjvf.fsf@gnu.org> <877dq5jp51.fsf@gmx.net> <83im9pmh0v.fsf@gnu.org> <106736d6-1732-3f24-15c5-af7bcfd688c6@yandex.ru> <83blfhmdho.fsf@gnu.org> <247a8edb-7b70-ad32-1ba1-43b5458a82b0@yandex.ru> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7745"; mail-complaints-to="usenet@ciao.gmane.io" Cc: stephen.berman@gmx.net, emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Nov 29 16:07:26 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kjOIQ-0001tn-3x for ged-emacs-devel@m.gmane-mx.org; Sun, 29 Nov 2020 16:07:26 +0100 Original-Received: from localhost ([::1]:34260 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kjOIP-0001tx-62 for ged-emacs-devel@m.gmane-mx.org; Sun, 29 Nov 2020 10:07:25 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53642) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kjOHa-0001Tw-PE for emacs-devel@gnu.org; Sun, 29 Nov 2020 10:06:34 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:35027) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kjOHa-0000Mq-1p; Sun, 29 Nov 2020 10:06:34 -0500 Original-Received: from [176.228.60.248] (port=1396 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kjOHZ-0004JC-Ff; Sun, 29 Nov 2020 10:06:33 -0500 In-Reply-To: <247a8edb-7b70-ad32-1ba1-43b5458a82b0@yandex.ru> (message from Dmitry Gutov on Sat, 28 Nov 2020 23:04:10 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:260006 Archived-At: > Cc: stephen.berman@gmx.net, emacs-devel@gnu.org > From: Dmitry Gutov > Date: Sat, 28 Nov 2020 23:04:10 +0200 > > >> Are you sure about that? Are we sure it won't make searching binary > >> files slower, for example? > > > > It will be slower, but more useful: by default Grep just says "Binary > > file foo matches". > > Do we want to search the "binary" files at all? We don't. I still hope to understand why -a was needed in this case. Stephen? > > We should support Grep regardless, since not everyone will have > > ripgrep. And in any case, "C-x RET c" will be needed with it as well, > > no? > > I'd have to test it explicitly to say for sure, but: > > ripgrep supports searching files in text encodings other than UTF-8, > such as UTF-16, latin-1, GBK, EUC-JP, Shift_JIS and more. (Some > support for automatically detecting UTF-16 is provided. Other text > encodings must be specifically specified with the -E/--encoding flag.) > > https://blog.burntsushi.net/ripgrep/#pitch What is not clear to me is whether the _output_ is always in some fixed encoding, like UTF-8. That doesn't seem to be stated in the docs there.