unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Pankaj Jangid <pankaj@codeisgreat.org>
To: 55477@debbugs.gnu.org
Subject: bug#55477: 29.0.50; flymake-goto-next-eror shows terminal like color codes in mini buffer
Date: Tue, 17 May 2022 21:57:23 +0530	[thread overview]
Message-ID: <871qws5dlg.fsf@codeisgreat.org> (raw)
In-Reply-To: <87a6bg5wrt.fsf@codeisgreat.org>

[-- Attachment #1: Type: text/plain, Size: 500 bytes --]

Pankaj Jangid <pankaj@codeisgreat.org> writes:

> I have an elisp buffer with some flymake errors. When I call
> "flymake-goto-next-error" the point moves to the error location and
> displays the error in minibuffer like this,
>
> ‘replace-string’ is for interactive use only; use ‘search-forward’ and ‘replace-match’ instead.
> user-error: Minibuffer window is not active
>
I should have sent screenshot in the first place. It appears like this (screenshot),


[-- Attachment #2: Screenshot from 2022-05-17 21-54-48.png --]
[-- Type: image/png, Size: 24943 bytes --]

  reply	other threads:[~2022-05-17 16:27 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 [this message]
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

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=871qws5dlg.fsf@codeisgreat.org \
    --to=pankaj@codeisgreat.org \
    --cc=55477@debbugs.gnu.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).