unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Carlos Pita <carlosjosepita@gmail.com>
To: behrmann@physik.fu-berlin.de, 32344@debbugs.gnu.org, eggert@cs.ucla.edu
Subject: bug#32344:
Date: Sun, 13 Oct 2019 16:24:31 -0300	[thread overview]
Message-ID: <CAELgYhd+R_h5ds6kYMQZ_v1ogGwQg-c+S7mrpFHtdJAoOWJwLQ@mail.gmail.com> (raw)
In-Reply-To: <CAELgYhdBRqHo=Zms5sjEjGQM3Yz_Zfon4iiqhc1X96FHzrFjZQ@mail.gmail.com>

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

Forgot the screenshots.

[-- Attachment #2: Screenshot from 2019-10-13 16-16-25.png --]
[-- Type: image/png, Size: 16434 bytes --]

[-- Attachment #3: Screenshot from 2019-10-13 16-21-40.png --]
[-- Type: image/png, Size: 19457 bytes --]

  reply	other threads:[~2019-10-13 19:24 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       ` Carlos Pita [this message]
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=CAELgYhd+R_h5ds6kYMQZ_v1ogGwQg-c+S7mrpFHtdJAoOWJwLQ@mail.gmail.com \
    --to=carlosjosepita@gmail.com \
    --cc=32344@debbugs.gnu.org \
    --cc=behrmann@physik.fu-berlin.de \
    --cc=eggert@cs.ucla.edu \
    /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).