From: Gaby Launay via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 32344@debbugs.gnu.org
Subject: bug#32344: [PATCH] 26.3/27 Option to avoid comint override colorization provided by major modes
Date: Mon, 14 Oct 2019 17:16:03 +0000 [thread overview]
Message-ID: <Y32ulz9vZ8FyQ-0UxcekxdcAmmIbREQ-Zf85Mk6jm-dR5kSALXxg44JChbOOKZ4TBe8OZOdp-eiMx4Iww73LPXJdIb8dkYfDgilahf6_KUc=@protonmail.com> (raw)
In-Reply-To: <87h8kdwro4.fsf@gmail.com>
Elpy maintainer here.
The advice works fine for me as well (for quite a long time now).
But Elpy tries to offer an out-of-the-box IDE, and persistent python font coloring in the shell would be very nice.
I tested Carlos' two patches just now and it works like a charm for me.
Let me know if there is anything I can do to help.
--
next prev parent reply other threads:[~2019-10-14 17:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 0:14 bug#32344: 26.1; Option to avoid comint highlighting input Carlos Pita
2018-08-02 1:19 ` bug#32344: Carlos Pita
2018-09-12 17:04 ` bug#32344: Carlos Pita
2018-09-17 16:36 ` bug#32344: (no subject) Jörg Behrmann
2019-10-13 17:18 ` bug#32344: Carlos Pita
2019-10-13 18:36 ` bug#32344: Carlos Pita
2019-10-13 19:23 ` bug#32344: Carlos Pita
2019-10-13 19:24 ` bug#32344: Carlos Pita
2019-10-13 21:53 ` bug#32344: [PATCH] 26.3/27 Option to avoid comint override colorization provided by major modes Carlos Pita
2019-10-21 20:39 ` Carlos Pita
2020-08-10 12:51 ` Lars Ingebrigtsen
2020-08-19 11:11 ` Lars Ingebrigtsen
2019-10-20 15:57 ` bug#32344: Juri Linkov
2019-10-14 17:16 ` Gaby Launay via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2019-10-21 20:53 ` bug#32344: Add option to keep colorization in comint, use it in python.el Carlos Pita
2019-10-22 18:25 ` Carlos Pita
2019-10-22 20:37 ` Juri Linkov
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='Y32ulz9vZ8FyQ-0UxcekxdcAmmIbREQ-Zf85Mk6jm-dR5kSALXxg44JChbOOKZ4TBe8OZOdp-eiMx4Iww73LPXJdIb8dkYfDgilahf6_KUc=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=32344@debbugs.gnu.org \
--cc=gaby.launay@protonmail.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 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).