From: Dmitry Gutov <dmitry@gutov.dev>
To: Matthias Meulien <orontee@gmail.com>
Cc: 75379@debbugs.gnu.org
Subject: bug#75379: 30.0.93; project-find-regexp expects "C" or "en" locale
Date: Mon, 6 Jan 2025 03:32:19 +0200 [thread overview]
Message-ID: <9e83141a-f870-463f-892f-1f8c1146a82a@gutov.dev> (raw)
In-Reply-To: <CAFEQCfCY3ZtfeUmnyrYH0c6KjWD37SjC2hFLdzOSoPLDiynpsA@mail.gmail.com>
On 05/01/2025 23:10, Matthias Meulien wrote:
> Thanks for the detailed report.
>
>
> You're welcome.
>
> I feel a bit culprit since I lived with that bug for such a long time
> and only started debugging today... Shame on me.
Late is certainly better than never.
> (...) About using LANG specifically, any chance that it might
> interfere with
> the system's configured encoding, e.g. UTF-8 vs other? In your example,
> does searching for accented characters work as well?
>
>
> Yes. I added LANG=C then checked succesfully that search succeed with
> french guillemet «, accented letters é, ç, and non-breaking space.
Thanks, that's a good sign. Perhaps someone else with experience in
process output encoding could confirm that this is generally a sane
approach, one that shouldn't lead to fewer matches caused by encoding
mismatch.
> IIUC we can try LC_MESSAGES as the more specialized var. Does
> LC_MESSAGES=en work as well?
>
>
> No. Matches in binary files make the search fail in that case.
Hmm, what about LC_MESSAGES=C?
If neither works, could you try that approach in the terminal? Does it
result in French text anyway, meaning this variable doesn't affect the
language in Grep?
prev parent reply other threads:[~2025-01-06 1:32 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
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 [this message]
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=9e83141a-f870-463f-892f-1f8c1146a82a@gutov.dev \
--to=dmitry@gutov.dev \
--cc=75379@debbugs.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).