From: Eli Zaretskii <eliz@gnu.org>
To: Pankaj Jangid <pankaj@codeisgreat.org>
Cc: acm@muc.de, larsi@gnus.org, eggert@cs.ucla.edu,
55477-done@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 21:20:47 +0300 [thread overview]
Message-ID: <83czg9crk0.fsf@gnu.org> (raw)
In-Reply-To: <87k0ahqtrp.fsf@codeisgreat.org> (message from Pankaj Jangid on Thu, 19 May 2022 23:39:14 +0530)
> From: Pankaj Jangid <pankaj@codeisgreat.org>
> Cc: Paul Eggert <eggert@cs.ucla.edu>, larsi@gnus.org, acm@muc.de,
> 55477@debbugs.gnu.org
> Date: Thu, 19 May 2022 23:39:14 +0530
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > This has nothing to do with quoting style, nor with Alan's "symbols
> > with positions" changes. The problem was that Flymake doesn't by
> > itself know which encoding to use for the files it checks and for
> > communicating with backend processes; when that is specific to the
> > major-mode (as in the case of ELisp, where we use UTF-8 by default),
> > the backend should arrange for that.
> >
> > I hope I fixed that now on the master branch.
>
> The bug is fixed now. Thanks a lot.
Great, thanks for testing. Closing.
prev parent reply other threads:[~2022-05-19 18:20 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
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 [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=83czg9crk0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55477-done@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=eggert@cs.ucla.edu \
--cc=larsi@gnus.org \
--cc=pankaj@codeisgreat.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).