unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Carlos Pita <carlosjosepita@gmail.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 32390@debbugs.gnu.org
Subject: bug#32390: 26.1; python.el: cleanup font lock buffer after input is sent
Date: Fri, 31 Aug 2018 08:56:58 -0300	[thread overview]
Message-ID: <CAELgYhfeyi3g1uRXprQPcdanCYPBrNSEuTsLr5ExfB-H-pj0tw@mail.gmail.com> (raw)
In-Reply-To: <87woshvk7a.fsf@gmail.com>

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

My report was for ipython. I've attached a screenshot showing the problem.

The way I'm fixing this issue at the moment is by patching
python-shell-font-lock-comint-output-filter-function like this:

(defun python-shell-font-lock-comint-output-filter-function (output)
  "Clean up the font-lock buffer after any OUTPUT."
  (if (and (python-shell-comint-end-of-output-p
            (ansi-color-filter-apply output))
           (not (string-match "\\.\\.\\.: $" output)))
      ;; If output is other than an input prompt then "real" output has
      ;; been received and the font-lock buffer must be cleaned up.
      (python-shell-font-lock-cleanup-buffer)
    ;; Otherwise just add a newline.
    (python-shell-font-lock-with-font-lock-buffer
      (goto-char (point-max))
      (newline)))
  output)

[-- Attachment #2: Screenshot_2018-08-31_08:54:00.png --]
[-- Type: image/png, Size: 14329 bytes --]

  reply	other threads:[~2018-08-31 11:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-07 18:49 bug#32390: 26.1; python.el: cleanup font lock buffer after input is sent Carlos Pita
2018-08-07 19:10 ` bug#32390: Carlos Pita
2018-08-07 19:34   ` bug#32390: Carlos Pita
2018-08-07 19:52     ` bug#32390: Carlos Pita
2018-08-07 20:28       ` bug#32390: Carlos Pita
2018-09-06  2:32       ` bug#32390: [ipython 6.x] unmatched quotes break fontification in run-python Noam Postavsky
2018-08-23  3:24 ` bug#32390: 26.1; python.el: cleanup font lock buffer after input is sent Noam Postavsky
2018-08-31 11:56   ` Carlos Pita [this message]
2018-09-01  3:01     ` Noam Postavsky
2018-09-05 15:38       ` Carlos Pita
2018-09-06  2:27         ` Noam Postavsky
2018-09-12 16:56           ` Carlos Pita
2018-12-04 22:35             ` Carlos Pita
2018-12-05 16:00               ` Carlos Pita
2019-01-03  5:43                 ` Carlos Pita
2019-10-15  0:21                   ` Noam Postavsky
2019-10-15  0:27                     ` Carlos Pita
2019-10-15  0:30                       ` Carlos Pita
2019-10-15  0:36                         ` Lars Ingebrigtsen
2019-10-15  0:40                         ` Noam Postavsky
2019-02-14 11:50 ` bug#32390: (no subject) Carlos Pita

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=CAELgYhfeyi3g1uRXprQPcdanCYPBrNSEuTsLr5ExfB-H-pj0tw@mail.gmail.com \
    --to=carlosjosepita@gmail.com \
    --cc=32390@debbugs.gnu.org \
    --cc=npostavs@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 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).