all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: <miha@kamnitnik.top>
Cc: 58169@debbugs.gnu.org, Augusto Stoffel <arstoffel@gmail.com>,
	Visuwesh <visuweshm@gmail.com>
Subject: bug#58169: 29.0.50; comint-fl-mode fontifies the output
Date: Fri, 30 Sep 2022 15:38:44 +0200	[thread overview]
Message-ID: <87edvt56e3.fsf@gnus.org> (raw)
In-Reply-To: <8735c976a6.fsf@miha-pc> (miha@kamnitnik.top's message of "Fri, 30 Sep 2022 07:58:09 +0200")

<miha@kamnitnik.top> writes:

>> Quickly hijacking this bug report to say: can we please announce
>> comint-fl-mode in NEWS, and say how to turn it off?  I was confused when
>> M-x shell randomly started to fontify the input line despite me
>> disabling every font-lock related thing in *shell* buffers.
>
> Thanks for reporting, I'll have time to work one these issues in the
> afternoon.

And I think we should probably rename it to `comint-font-lock-mode',
because the current name is obscure.





  reply	other threads:[~2022-09-30 13:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29 16:24 bug#58169: 29.0.50; comint-fl-mode fontifies the output Augusto Stoffel
2022-09-30  1:55 ` Visuwesh
2022-09-30  5:58   ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-30 13:38     ` Lars Ingebrigtsen [this message]
2022-09-30 18:38       ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-30 18:26         ` Lars Ingebrigtsen
2022-09-30 19:22           ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-30 19:14             ` Lars Ingebrigtsen
2022-10-01 14:43             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-06 18:37               ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87edvt56e3.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=58169@debbugs.gnu.org \
    --cc=arstoffel@gmail.com \
    --cc=miha@kamnitnik.top \
    --cc=visuweshm@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.