GNU bug report logs - #33959
26.1.90; python.el font-lock buffer wreaks havoc when company is enabled

Previous Next

Full log

Message #50 received at 33959 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> gmail.com>
To: Carlos Pita <carlosjosepita <at> gmail.com>
Cc: 33959 <at> debbugs.gnu.org
Subject: Re: bug#33959: 26.1.90;
 python.el font-lock buffer wreaks havoc when company is enabled
Date: Fri, 10 May 2019 23:51:30 -0400

Noam Postavsky <npostavs <at> gmail.com> writes:

> Noam Postavsky <npostavs <at> gmail.com> writes:
>
>> Carlos Pita <carlosjosepita <at> gmail.com> writes:
>>
>>> I'm unable to get your output, here the font lock buffer always
>>> contains one line.
>>
>> Hmm, it might have to do with the fact that I'm running ipython over
>> TRAMP, since my main box doesn't have IPython 6.x.  But I suspect that
>> only affects the timing, so that it's still theoretically possible
>> (although less likely) for it to happen when running locally.
>
> I installed IPython 6.5.0 locally using pip, and I still see the same
> behaviour (including repeated input prompt numbers).

I think I figured out what the difference is: I forgot to add
--simple-prompt to python-shell-interpreter-args.  After doing that,
your patch does indeed fix the problem.  I'd still like a deterministic
test, though, since this bug is such a pain to reproduce.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.