Re: Missing process status in *Python* buffer

Matthias Meulien <[email protected]> writes:

> With Emacs 30.1 and 32.0.50 (both started with -Q), after `run-python` is
> called, the mode-line of the created `*Python*` buffer doesn't display any
> process information despite the following line in the definition of the
> major mode `inferior-python-mode`:
>
> ``` elisp
>   (setq mode-line-process '(":%s"))
> ```
> and the local value of `mode-line-process` is nil in that buffer.

I can reproduce this, please report it.  This problem doesn't seem to
occur every time.  Sometimes, it also works as expected.  Tested 5 times
with a fresh emacs -Q, and two times it just worked.  3 times it didn't.

Something like this is happening (recorded using my configured Emacs):

| 1 → set mode-line-process := nil  locally in #<buffer *Python*>
|   (comint-redirect-cleanup)
|   (comint-redirect-preoutput-filter "on__  \15\n")
|   (comint-redirect-filter ...)
|   (python-shell-accept-process-output #<process Python> 1.0 "1__dummy_completion__.*\n")
|   (python-shell-completion-native-get-completions #<process Python> "_")
|   (python-shell-completion-native-try)
|   (python-shell-completion-native-setup)
|   (python-shell-completion-native-turn-on-maybe t)
|   (python-shell-completion-native-turn-on-maybe-with-msg)
|   (python-shell-comint-watch-for-first-prompt-output-filter ...)
|   (comint-output-filter #<process Python> #("Python 3.11.2 ...))

Something seems to be wrong with `comint-redirect-cleanup' - whatever
that is.


Michael.