From: Noam Postavsky <npostavs@gmail.com>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: 31115@debbugs.gnu.org
Subject: bug#31115: 26.1; python shell flicker
Date: Sat, 14 Apr 2018 10:42:12 -0400 [thread overview]
Message-ID: <87lgdpkfy3.fsf@gmail.com> (raw)
In-Reply-To: <4b3cf81a-bff1-2894-52ee-203782c4554b@easy-emacs.de> ("Andreas \=\?utf-8\?Q\?R\=C3\=B6hler\=22's\?\= message of "Thu, 12 Apr 2018 08:20:39 +0200")
severity 31115 minor
tags 31115 + confirmed
quit
Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
> On 09.04.2018 20:19, Charles A. Roelli wrote:
>> emacs -q
>> M-x run-python RET C-x o
>>
>> Now press and hold down RET: a lot of prompts fly by, and as soon as
>> point reaches the bottom of the window, there is some flicker where
>> the cursor momentarily appears centered (as if `recenter' was run) and
>> simultaneously all the text in the buffer blinks as if the whole
>> screen was cleared and redrawn. In contrast, if you try this same
>> recipe in a normal shell buffer from M-x shell, there won't be any
>> flicker.
> Can't reproduce with GNU Emacs 26.1 (build 1, i686-pc-linux-gnu, GTK+
> Version 3.14.5) of 2018-04-10 at Debian
I can reproduce on Emacs 26, both lucid and GTK builds. Seems pretty
straightforward: point reaches the end of buffer, so Emacs autoscrolls
by half a window, then python-comint-postoutput-scroll-to-bottom kicks
in and scrolls back to the bottom.
>> A naive fix is to comment out the meat of python-comint-postoutput-
>> scroll-to-bottom, and reevaluate it:
>>
>> (defun python-comint-postoutput-scroll-to-bottom (output)
>> "Faster version of `comint-postoutput-scroll-to-bottom'.
>> Avoids `recenter' calls until OUTPUT is completely sent."
>> ;; (when (and (not (string= "" output))
>> ;; (python-shell-comint-end-of-output-p
>> ;; (ansi-color-filter-apply output)))
>> ;; (comint-postoutput-scroll-to-bottom output))
>> output)
Right, that help because Emacs no longer scrolls the window back to the
bottom. Seems like (setq scroll-conservatively 1) works better to
preserve the original behaviour (I feel like that's too easy, so I must
be missing something though).
next prev parent reply other threads:[~2018-04-14 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 18:19 bug#31115: 26.1; python shell flicker Charles A. Roelli
2018-04-12 6:20 ` Andreas Röhler
2018-04-14 14:42 ` Noam Postavsky [this message]
2022-05-07 11:56 ` Lars Ingebrigtsen
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=87lgdpkfy3.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=31115@debbugs.gnu.org \
--cc=andreas.roehler@easy-emacs.de \
/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).