unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: Matthias Meulien <orontee@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 75379@debbugs.gnu.org
Subject: bug#75379: 30.0.93; project-find-regexp expects "C" or "en" locale
Date: Tue, 7 Jan 2025 16:24:29 +0200	[thread overview]
Message-ID: <af396fc8-00cd-4bb1-b50d-22149b420a4c@gutov.dev> (raw)
In-Reply-To: <CAFEQCfCLS-_8ZS9zvfjxaV38B1m4wTVR-eUtTLEXch9xMHVSTA@mail.gmail.com>

On 07/01/2025 07:42, Matthias Meulien wrote:
> Why not keep user locale setting and keep current grep args, but send a 
> generated file with NUL chars to collect the output message and make 
> current check generating the error be dynamically generated?

More complicated. We're not sure which programs will end in the 
customization of xref-search-program-alist, and whether each of them 
will detect binary files the same way.

Also Ripgrep outputs somewhat varying text like:

test/manual/etags/f-src/entry.strange.gz: binary file matches (found 
"\0" byte around offset 23)
test/manual/etags/cp-src/clheir.cpp.gz: binary file matches (found "\0" 
byte around offset 20)

Specifying the language from an environment var seems like the most 
straightforward approach still.





  parent reply	other threads:[~2025-01-07 14:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-05 10:35 bug#75379: 30.0.93; project-find-regexp expects "C" or "en" locale Matthias Meulien
2025-01-05 18:03 ` Dmitry Gutov
2025-01-05 18:46   ` Eli Zaretskii
2025-01-05 19:35     ` Dmitry Gutov
2025-01-05 20:16       ` Eli Zaretskii
2025-01-07 14:17         ` Dmitry Gutov
2025-01-07 14:23           ` Eli Zaretskii
2025-01-07 14:26             ` Dmitry Gutov
2025-01-07 14:50               ` Eli Zaretskii
2025-01-05 21:22     ` Matthias Meulien
2025-01-05 21:29       ` Matthias Meulien
2025-01-06 13:03         ` Eli Zaretskii
2025-01-06  1:55       ` Dmitry Gutov
2025-01-06 12:36         ` Matthias Meulien
2025-01-06 12:42           ` Matthias Meulien
2025-01-06 14:13             ` Dmitry Gutov
2025-01-06 14:11           ` Dmitry Gutov
2025-01-07  5:42             ` Matthias Meulien
2025-01-07 12:45               ` Eli Zaretskii
2025-01-07 14:24               ` Dmitry Gutov [this message]
2025-01-06 17:36         ` Juri Linkov
2025-01-06 20:33           ` Dmitry Gutov
2025-01-07 17:39             ` Juri Linkov
2025-01-07 19:38               ` Dmitry Gutov
2025-01-08  7:48                 ` Juri Linkov
2025-01-06 13:02       ` Eli Zaretskii
2025-01-06 14:13         ` Dmitry Gutov
2025-01-05 21:10   ` Matthias Meulien
2025-01-06  1:32     ` Dmitry Gutov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=af396fc8-00cd-4bb1-b50d-22149b420a4c@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=75379@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=orontee@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).