unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Shitikanth <shitikanth1@gmail.com>
To: 47679@debbugs.gnu.org
Subject: bug#47679: 28.0.50; python-shell-switch-to-shell redisplay bug
Date: Sat, 10 Apr 2021 02:33:36 +0530	[thread overview]
Message-ID: <CALjXJSQxpz6pZqA-ho2nL2sC7B-YdB_i8FZaYSnHn=yu1KrC7Q@mail.gmail.com> (raw)
In-Reply-To: <87k0pb89m2.fsf@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 968 bytes --]

Proposed fix.

On Sat, 10 Apr 2021 at 02:22, Shitikanth Kashyap <shitikanth1@gmail.com>
wrote:

> Steps to reproduce:
> 1. emacs -Q
> 2. Open any python file
> 3. Press "C-c C-p"  to start interpreter
> 4. Press "C-c C-z" from the file's window to switch to interpreter
> 5. Go back to file's window with "C-x o" and repeat from 4 a few times.
>
> There is notable lag (sometimes as much as a few seconds) between
> pressing the keybinding "C-c C-z" in file's window before the cursor
> appears to be ready on the interpreter's window. The state of the cursor
> in the two windows after the command appears to be indeterministic and
> inconsistent.
>
> The issue seems to be that the display of the two windows is not updated
> even though internally emacs has changed the focus to the correct
> window. For example, it is possible to start typing in the interpreter
> window immediately after the command, even though the cursor does not
> seem to ready.
>
>
>
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 1402 bytes --]

[-- Attachment #2: 0001-Fix-python-shell-switch-to-shell-redisplay-bug.patch --]
[-- Type: application/octet-stream, Size: 837 bytes --]

From b2633cb4bc7b259839f1ac3a6215e839c2a74be7 Mon Sep 17 00:00:00 2001
From: Shitikanth Kashyap <shitikanth1@gmail.com>
Date: Sat, 10 Apr 2021 01:32:51 +0530
Subject: [PATCH] Fix python-shell-switch-to-shell redisplay bug

---
 lisp/progmodes/python.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/progmodes/python.el b/lisp/progmodes/python.el
index e5c15d148f..3af0bdde2e 100644
--- a/lisp/progmodes/python.el
+++ b/lisp/progmodes/python.el
@@ -3385,7 +3385,7 @@ python-shell-switch-to-shell
 t when called interactively."
   (interactive "p")
   (pop-to-buffer
-   (process-buffer (python-shell-get-process-or-error msg)) nil t))
+   (process-buffer (python-shell-get-process-or-error msg)) nil 'mark-for-redisplay))
 
 (defun python-shell-send-setup-code ()
   "Send all setup code for shell.
-- 
2.30.2


  reply	other threads:[~2021-04-09 21:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 20:51 bug#47679: 28.0.50; python-shell-switch-to-shell redisplay bug Shitikanth Kashyap
2021-04-09 21:03 ` Shitikanth [this message]
2021-04-12  8:44   ` Lars Ingebrigtsen
2021-04-12 18:25     ` Shitikanth
2021-04-13  7:34       ` 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='CALjXJSQxpz6pZqA-ho2nL2sC7B-YdB_i8FZaYSnHn=yu1KrC7Q@mail.gmail.com' \
    --to=shitikanth1@gmail.com \
    --cc=47679@debbugs.gnu.org \
    /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).