From: Paul Eggert <eggert@cs.ucla.edu>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Alan Mackenzie <acm@muc.de>,
55477@debbugs.gnu.org, Pankaj Jangid <pankaj@codeisgreat.org>
Subject: bug#55477: 29.0.50; flymake-goto-next-eror shows terminal like color codes in mini buffer
Date: Wed, 18 May 2022 13:11:46 -0700 [thread overview]
Message-ID: <0d94334a-0ae2-d4b0-f448-e05196ef8951@cs.ucla.edu> (raw)
In-Reply-To: <87leuzdqxz.fsf@gnus.org>
On 5/18/22 04:24, Lars Ingebrigtsen wrote:
>> The above expression is returning "curve"; in all three environments,
>>
>> en_US.UTF-8
>> en_IN.UTF-8
>> en_IN
> That seems like a bug, because in the final environment, Emacs doesn't
> seem to be able to display the curved quote.
But Emacs *can* display curved quotes in that environment. It's
misdisplaying them as individual bytes, and that's the bug: it should
simply display the characters as-is.
This bug is not limited to quotes. Put this into a file t.el:
(defun δ-replace-string (from-string to-string)
(declare (interactive-only
"use `search-forward' and `replace-match' instead."))
(interactive))
(defun test-fun (obj)
(if (stringp obj)
(δ-replace-string "from" "to")))
run "LC_ALL=en_IN emacs -Q", visit the file, evaluate the first form,
and then do M-x flymake-mode followed by repeated uses of M-x
flymake-goto-next-error. It will eventually report the diagnostic:
‘δ-replace-string’ is for interactive use only; use ‘search-forward’
and ‘replace-match’ instead.
That is, the "δ" (which in UTF-8 is #xCE #xB4) is misinterpreted as the
two Latin-1 characters Î (#xCE) and ´ (#xB4).
I suspect that the problem is due to Alan's recent change to the meaning
of EQ. As I understand it, when byte-compiling, EQ doesn't mean the same
thing that it does ordinarily. But format-message (which is used by the
byte compiler) uses EQ to decide what to do, and it bases its decision
on whether the resulting string is unibyte or multibyte. Evidently this
new meaning of EQ is messing up format-message's internals.
I'll CC this to Alan to see whether he can provide some insight.
next prev parent reply other threads:[~2022-05-18 20:11 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 [this message]
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=0d94334a-0ae2-d4b0-f448-e05196ef8951@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=55477@debbugs.gnu.org \
--cc=acm@muc.de \
--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).