From: Pankaj Jangid <pankaj@codeisgreat.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 55477@debbugs.gnu.org
Subject: bug#55477: 29.0.50; flymake-goto-next-eror shows terminal like color codes in mini buffer
Date: Wed, 18 May 2022 09:02:14 +0530 [thread overview]
Message-ID: <875ym3ikht.fsf@codeisgreat.org> (raw)
In-Reply-To: <874k1ojakj.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 17 May 2022 20:09:00 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> It's supposed to work automatically, though. What's the value of your
> text-quoting-style variable? The default, nil, is supposed to result in
> using "plain" quotes when it can't display the curved ones.
>
> (text-quoting-style)
> => curve
>
> here, but it should have returned nil in the en_IN environment you were
> in, apparently.
The above expression is returning "curve"; in all three environments,
en_US.UTF-8
en_IN.UTF-8
en_IN
I did one more experiment. I tried with LANG=en_IN.UTF-8 and it was
working fine. The bug is reproducible only with LANG=en_IN.
And I guess the desktop environment sets LANG to just en_IN or en_US
when only one variant of English is enabled in the system locales. After
adding both in locales, switch language changes it to either en_US.UTF-8
or en_IN.UTF-8.
next prev parent reply other threads:[~2022-05-18 3:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 9:33 bug#55477: 29.0.50; flymake-goto-next-eror shows terminal like color codes in mini buffer Pankaj Jangid
2022-05-17 16:27 ` Pankaj Jangid
2022-05-17 16:30 ` Lars Ingebrigtsen
2022-05-17 16:55 ` Pankaj Jangid
2022-05-17 17:18 ` Lars Ingebrigtsen
2022-05-17 17:55 ` Pankaj Jangid
2022-05-17 18:02 ` Pankaj Jangid
2022-05-17 18:09 ` Lars Ingebrigtsen
2022-05-18 3:32 ` Pankaj Jangid [this message]
2022-05-18 11:18 ` Eli Zaretskii
2022-05-19 3:07 ` Pankaj Jangid
2022-05-18 11:24 ` Lars Ingebrigtsen
2022-05-18 20:11 ` Paul Eggert
2022-05-19 3:13 ` Paul Eggert
2022-05-19 4:54 ` Eli Zaretskii
2022-05-19 8:06 ` Eli Zaretskii
2022-05-19 18:09 ` Pankaj Jangid
2022-05-19 18:20 ` Eli Zaretskii
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=875ym3ikht.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--cc=55477@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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).