bug#70914: 29.3; Crashes often on Windows

[Simen Endsjø]

>> I found another issue. My files are stored in UTF-8 also on Windows.
>> Without setting Windows in the "Beta: Use UTF-8 everywhere", tools
>> like ripgrep will somehow interpret the files as latin-1. So I cannot
>> search for special characters in my language, and I even remember
>> having crashes happening when searching documents which includes them.
>
> Not sure how this is related to Emacs.  I only recommended not to
> customize Emacs to use UTF-8 by default; I said nothing about ripgrep
> or Windows in general.

But it seems emacs (or something therein) interprets utf-8 as ascii. As stated
later, the `(prefer-coding-system 'utf-8)` resolves this.

> You can keep your "Use UTF-8 everywhere" setting for Windows, just
> don't customize the coding-systems in Emacs to use UTF-8 by default.
>
> Or what am I missing?

I think `Use UTF-8 everywhere` will cause Windows to use UTF-8 rather than
UTF-16 many places, so any assumptions that it uses UTF-16 will fail. But I
might try to turn this on again to see if this helps.

On Wed, May 15, 2024 at 2:16 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Simen Endsjø <simendsjo@gmail.com>
> > Date: Wed, 15 May 2024 13:19:53 +0200
> > Cc: 70914@debbugs.gnu.org
> >
> > I found another issue. My files are stored in UTF-8 also on Windows.
> > Without setting Windows in the "Beta: Use UTF-8 everywhere", tools
> > like ripgrep will somehow interpret the files as latin-1. So I cannot
> > search for special characters in my language, and I even remember
> > having crashes happening when searching documents which includes them.
>
> Not sure how this is related to Emacs.  I only recommended not to
> customize Emacs to use UTF-8 by default; I said nothing about ripgrep
> or Windows in general.
>
> You can keep your "Use UTF-8 everywhere" setting for Windows, just
> don't customize the coding-systems in Emacs to use UTF-8 by default.
>
> Or what am I missing?