unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Glenn Morris <rgm@gnu.org>
Cc: 27154@debbugs.gnu.org, Diego Fernandez <difernan@redhat.com>
Subject: bug#27154: 25.2; python.el shell does not respect getpass.getpass prompt
Date: Wed, 31 May 2017 19:48:19 -0400	[thread overview]
Message-ID: <87poeo37wc.fsf@users.sourceforge.net> (raw)
In-Reply-To: <omshjkyidc.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 31 May 2017 14:46:23 -0400")

Glenn Morris <rgm@gnu.org> writes:

> I see comint-watch-for-password-prompt was taken out a few years ago (a6dc66a),
> for performance reasons, https://debbugs.gnu.org/16875 . Though from the
> numbers quoted there, it doesn't look like it was causing any problem.

Yeah, it looks like it was just a casualty of over zeolous streamlining.

Andreas Röhler <andreas.roehler@easy-emacs.de> writes:

> Hmm, not working here - see attachment.
>
> Also when typing the password, it is not echoed. Just dots appear in
> minibuffer.

That means it's working.

> BTW comint-watch-for-password-prompt was already in comint mode -
> another add-hook seems redundant.

Yeah, the problem is that python-mode removes it.

> Looks like the inconvenient results from Python itself - see outside-emacs.png

Sure, the filter isn't supposed to prevent your python program from
printing passwords.





  parent reply	other threads:[~2017-05-31 23:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 20:50 bug#27154: 25.2; python.el shell does not respect getpass.getpass prompt Diego Fernandez
2017-05-31 18:35 ` Glenn Morris
2017-05-31 18:46   ` Glenn Morris
2017-05-31 19:08     ` Diego Fernandez
2017-05-31 19:54       ` Andreas Röhler
2017-05-31 23:48     ` npostavs [this message]
2017-06-03  0:07       ` Glenn Morris

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=87poeo37wc.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=27154@debbugs.gnu.org \
    --cc=difernan@redhat.com \
    --cc=rgm@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).