From: Lars Ingebrigtsen <larsi@gnus.org>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: 32390@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>
Subject: bug#32390: 26.1; python.el: cleanup font lock buffer after input is sent
Date: Tue, 15 Oct 2019 02:36:56 +0200 [thread overview]
Message-ID: <87k196rgif.fsf@gnus.org> (raw)
In-Reply-To: <CAELgYheESybQNzQ=aR4sFqXzOjwt_mqChHkT1+BYC6GO=dWFVg@mail.gmail.com> (Carlos Pita's message of "Mon, 14 Oct 2019 21:30:31 -0300")
Carlos Pita <carlosjosepita@gmail.com> writes:
> Also, shouldn't this be applied to emacs-26 besides of master? I mean,
> it's a bugfix.
There won't be any more Emacs 26 releases -- nothing is applied to that
branch at present.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-15 0:36 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
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 [this message]
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=87k196rgif.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=32390@debbugs.gnu.org \
--cc=carlosjosepita@gmail.com \
--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).