From: Carlos Pita <carlosjosepita@gmail.com>
To: 32344@debbugs.gnu.org
Subject: bug#32344:
Date: Wed, 1 Aug 2018 22:19:13 -0300 [thread overview]
Message-ID: <CAELgYheN1yxy+PgJmTZL+FCO8KXQR_HwiTdEvk7C1TseVPFwHg@mail.gmail.com> (raw)
In-Reply-To: <87h8kdwro4.fsf@gmail.com>
Here is a workaround:
(advice-add 'comint-send-input
:around (lambda (f &rest args)
(when (eq major-mode 'inferior-python-mode)
(cl-letf (((symbol-function 'g)
(symbol-function 'add-text-properties))
((symbol-function 'add-text-properties)
(lambda (start end properties
&optional object)
(unless (eq (nth 3 properties)
'comint-highlight-input)
(g start end properties object)))))
(apply f args)))))
next prev parent reply other threads:[~2018-08-02 1:19 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 ` Carlos Pita [this message]
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 ` bug#32344: [PATCH] 26.3/27 Option to avoid comint override colorization provided by major modes Gaby Launay via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=CAELgYheN1yxy+PgJmTZL+FCO8KXQR_HwiTdEvk7C1TseVPFwHg@mail.gmail.com \
--to=carlosjosepita@gmail.com \
--cc=32344@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).