From: Live System User <nyc4bos@aol.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 25753@debbugs.gnu.org, "Charles A. Roelli" <charles@aurox.ch>
Subject: bug#25753: 25.2; Python mode shell interaction not working 100%
Date: Sun, 19 Feb 2017 14:39:00 -0500 [thread overview]
Message-ID: <87d1eermwb.fsf@aol.com> (raw)
In-Reply-To: <CAM-tV--CV5jfJS3S0J6toHFjfB7suEhx0ASVKOpBc8ONknjfGQ@mail.gmail.com> (Noam Postavsky's message of "Sun, 19 Feb 2017 10:26:45 -0500")
Noam Postavsky <npostavs@users.sourceforge.net> writes:
> On Sun, Feb 19, 2017 at 10:14 AM, Live System User <nyc4bos@aol.com> wrote:
>>>
>>> It might be something macOS specific, because I don't see any problems
>>> on Arch GNU/Linux with python 2.7.13.
>>
>> I see the problem on GNU/Linux (Fedora):
>>
>> Warning (python): Your ‘python-shell-interpreter’ doesn’t seem to
> [...]
>> In GNU Emacs 25.1.1 (x86_64-redhat-linux-gnu, GTK+ Version 3.20.9)
>> of 2016-10-13 built on buildvm-05.phx2.fedoraproject.org
>> Windowing system distributor 'Fedora Project', version 11.0.11803000
>
> Do you see this with 25.2-rc1 on GNU/Linux though?
Fedora doesn't have that version available currently.
>
> There *was* a change since 25.1 (although supposedly that only
> affected python 3). Do you have "set colored-stats on" in your
> ~/.inputrc? There was a report in #24401 of that causing trouble.
I don't have a ~/.input file.
I did, however, look into the Python modules having to do with
"readline"(completion).
I discovered that if I used the "readline" from "pyrepl.py"instead
of the standard default one, then even though that warning still
occured in a *Warning* buffer in Emacs, I never saw it -- I just
saw the *Python* buffer and my source buffer, as expected.
I haven't looked deeper as to why "pyrepl"'s readline is able to
not display the *Warning* buffer while Python's standard default
readline displays the *Warning* buffer until it is dismissed.
Thanks.
next prev parent reply other threads:[~2017-02-19 19:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 16:07 bug#25753: 25.2; Python mode shell interaction not working 100% Charles A. Roelli
2017-02-16 17:54 ` Eli Zaretskii
2017-02-18 17:44 ` npostavs
2017-02-19 15:14 ` Live System User
2017-02-19 15:26 ` Noam Postavsky
2017-02-19 19:39 ` Live System User [this message]
2017-02-19 20:00 ` Noam Postavsky
2017-02-19 21:32 ` Live System User
2017-02-20 1:30 ` npostavs
2017-02-20 22:34 ` Live System User
2017-02-21 1:46 ` npostavs
2017-02-21 3:32 ` Live System User
2017-02-21 13:35 ` npostavs
2017-02-21 23:17 ` Live System User
2017-02-22 1:40 ` npostavs
2017-02-22 19:43 ` Charles A. Roelli
2017-02-23 14:20 ` npostavs
2017-02-24 10:19 ` Charles A. Roelli
2017-02-25 14:11 ` Charles A. Roelli
2017-02-25 14:34 ` npostavs
2017-02-25 22:28 ` Charles A. Roelli
2017-02-27 2:14 ` npostavs
2017-02-28 10:34 ` Charles A. Roelli
2017-02-28 14:07 ` npostavs
2017-02-28 15:56 ` Eli Zaretskii
2017-03-01 23:00 ` npostavs
2021-10-03 16:03 ` Carlos Pita
2021-10-03 16:31 ` Carlos Pita
2021-10-03 23:35 ` Carlos Pita
2021-10-03 23:55 ` Carlos Pita
2021-10-04 0:46 ` Carlos Pita
2021-10-04 15:05 ` Carlos Pita
2021-10-04 8:21 ` Augusto Stoffel
2021-10-04 15:31 ` Carlos Pita
2021-10-04 15:47 ` Augusto Stoffel
2023-08-11 17:55 ` bug#25753: 29.1; " Peter Mao
2023-08-25 5:32 ` Peter Mao
2023-08-25 6:31 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1eermwb.fsf@aol.com \
--to=nyc4bos@aol.com \
--cc=25753@debbugs.gnu.org \
--cc=charles@aurox.ch \
--cc=npostavs@users.sourceforge.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.