From: "shynur ." <one.last.kiss@outlook.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "71440@debbugs.gnu.org" <71440@debbugs.gnu.org>
Subject: bug#71440: Python Inferior Mode Can’t Recognize My Prompt
Date: Sun, 9 Jun 2024 10:49:19 +0000 [thread overview]
Message-ID: <PH0PR11MB747056A4303C7677135029B8D7C52@PH0PR11MB7470.namprd11.prod.outlook.com> (raw)
In-Reply-To: <8634pmbefs.fsf@gnu.org>
> I wonder how PS1 and PS2 are at all relevant when using
> python-shell-send-buffer? That function sends the buffer
> text to Python, so where do PS1 and PS2 come into play,
> and why does Python say "__PYTHON_EL_eval is not defined"
> just because you have PS1 and PS2 customized?
I know it’s *weird* but it just happened.
I gave the recipes in the original post for anyone to
reproduce it.
> If someone helps me understand that, maybe I will have
> further ideas.
How about CC this post to the maintainer(s) of ‘python.el’?
> How about defining PYTHONSTARTUP to point to a different
> file?
This makes it inconvenient to add or modify content to the
‘PYTHONSTARTUP’ file because each change needs to be synced
to another file that exists for Emacs.
next prev parent reply other threads:[~2024-06-09 10:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-08 16:29 bug#71440: Python Inferior Mode Can’t Recognize My Prompt shynur .
2024-06-08 16:53 ` Eli Zaretskii
2024-06-08 17:06 ` shynur .
2024-06-08 17:29 ` bug#71440: " Eli Zaretskii
2024-06-08 17:46 ` shynur .
2024-06-08 18:41 ` bug#71440: " Eli Zaretskii
2024-06-08 19:50 ` shynur .
2024-06-09 4:31 ` bug#71440: " Eli Zaretskii
2024-06-09 10:11 ` shynur .
2024-06-09 10:25 ` bug#71440: " Eli Zaretskii
2024-06-09 10:49 ` shynur . [this message]
2024-06-09 11:02 ` Eli Zaretskii
2024-06-09 15:26 ` kobarity
2024-06-09 15:40 ` bug#71440: Python Inferior Mode Canʼt " shynur .
2024-06-11 16:24 ` bug#71440: Python Inferior Mode Can’t " kobarity
2024-06-12 8:12 ` Eli Zaretskii
2024-06-12 13:09 ` kobarity
2024-06-12 16:57 ` shynur .
2024-06-13 14:24 ` kobarity
2024-06-15 10:45 ` Eli Zaretskii
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=PH0PR11MB747056A4303C7677135029B8D7C52@PH0PR11MB7470.namprd11.prod.outlook.com \
--to=one.last.kiss@outlook.com \
--cc=71440@debbugs.gnu.org \
--cc=eliz@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).