From: npostavs@users.sourceforge.net
To: charles@aurox.ch (Charles A. Roelli)
Cc: 25753@debbugs.gnu.org
Subject: bug#25753: 25.2; Python mode shell interaction not working 100%
Date: Sun, 26 Feb 2017 21:14:45 -0500 [thread overview]
Message-ID: <87innwe5wq.fsf@users.sourceforge.net> (raw)
In-Reply-To: <m2efylsy6b.fsf@aurox.ch> (Charles A. Roelli's message of "Sat, 25 Feb 2017 23:28:12 +0100")
charles@aurox.ch (Charles A. Roelli) writes:
> On Sat, Feb 25 2017 at 09:34:10 am, npostavs@users.sourceforge.net wrote:
>
>> Possibly setting `comint-process-echoes' could help, though I don't
>> understand why there is echoing in the first place.
>
> Thanks for the pointer to that variable. I ran this:
>
> (add-hook 'inferior-python-mode-hook (lambda () (setq comint-process-echoes t)))
>
> and the commands at the prompt stopped echoing, but the support
> functions still echoed. So it looks like the problem has to be fixed on
> the readline/libedit side of Python.
This thread[1] might be somewhat relevant:
The problem is that eshell tells subprocesses that they're running in
a terminal (e.g., when queried via hIsTerminalDevice), but always
echos user input itself regardless of the tty's ECHO attribute. This
confuses libedit, which assumes that if it's connected to a terminal
then it can turn off echoing in order to run its own rich line editor.
[1]: http://glasgow-haskell-users.haskell.narkive.com/vyeVJUEB/problem-with-echo-prompting-in-ghci-visible-in-emacs
> So it would seem that `sudo easy_install
> gnureadline' is the right thing to run. However that still does not fix
> the issue because python2.7/lib-dynload/ comes before
> python2.7/site-packages/ (where `gnureadline' is installed) in Python's
> $PATH equivalent, `sys.path'. The solution, then, is to reorder the
> path somehow or get `readline.so' out of the way (maybe by renaming it
> -- cleaner suggestions welcome).
I guess renaming should have the least amount of side-effects.
next prev parent reply other threads:[~2017-02-27 2:14 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
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 [this message]
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=87innwe5wq.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=25753@debbugs.gnu.org \
--cc=charles@aurox.ch \
/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.