From: Pankaj Jangid <pankaj@codeisgreat.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 55477@debbugs.gnu.org
Subject: bug#55477: 29.0.50; flymake-goto-next-eror shows terminal like color codes in mini buffer
Date: Thu, 19 May 2022 08:37:48 +0530 [thread overview]
Message-ID: <87mtferzi3.fsf@codeisgreat.org> (raw)
In-Reply-To: <83sfp7f5sm.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 18 May 2022 14:18:01 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> en_US.UTF-8
>> en_IN.UTF-8
>> en_IN
>
> What is the value of
>
> (default-value 'buffer-file-coding-system)
>
> in each of the 3 environments?
utf-8-unix
utf-8-unix
iso-latin-1-unix
respectively
> And also what does the below return in each of the 3 environments?
>
> (char-displayable-p ?‘)
#<font-object "-PfEd-DejaVu Sans Mono-regular-normal-normal-*-19-*-*-*-m-0-iso10646-1">
#<font-object "-PfEd-DejaVu Sans Mono-regular-normal-normal-*-19-*-*-*-m-0-iso10646-1">
#<font-object "-PfEd-DejaVu Sans Mono-regular-normal-normal-*-19-*-*-*-m-0-iso10646-1">
respectively
next prev parent reply other threads:[~2022-05-19 3:07 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
2022-05-18 11:18 ` Eli Zaretskii
2022-05-19 3:07 ` Pankaj Jangid [this message]
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=87mtferzi3.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--cc=55477@debbugs.gnu.org \
--cc=eliz@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).