From: Rahul Martim Juliato <rahuljuliato@gmail.com>
To: Glenn Morris <rgm@gnu.org>, 25596@debbugs.gnu.org
Subject: bug#25596: 25.1; Password not hidden
Date: Wed, 01 Mar 2017 14:27:15 -0300 [thread overview]
Message-ID: <86h93c6h70.fsf@gmail.com> (raw)
In-Reply-To: <86wpdaisui.fsf@gmail.com>
So I tested this way:
emacs -Q -f shell
export LC_ALL="C"
sudo ls
And BANG! password is prompted in a hidden way on the minibuffer!
(sudo presents its prompt in english)
So, is comint-password-prompt-regexp bugged? I recall that
eshell works fine. Also, it seems that recognizes sudo OR other stuff
(I'm not the best regex reader by the way).
I also tried on my Debian notebook, and the password for sudo
is prompted in english, so there's no problem there.
Glenn Morris <rgm@gnu.org> writes:
> Rahul Martim Juliato wrote:
>
>> emacs -Q -f shell
>>
>> inside of it:
>> sudo ls
>>
>> And then shell asks me for the password not hiding it when I type.
>
> Thanks. I see that in your initial report, you said the prompt was:
>
> [sudo] senha para eng:
>
>> I already tried a "solution" i found on-line by adding this to my .emacs file:
>>
>> (add-hook 'comint-output-filter-functions
>> 'comint-watch-for-password-prompt)
>
> This is already done by default.
>
>> And altough I'm using a brazillian portuguese system, sudo should
>> recognize the portuguese word "senha" as a passwork equivalent, or at
>> least recognize that the line asks for password with "[sudo]".
>
> Emacs has the variable password-word-equivalents, which includes "senha"
> by default.
>
> The problem is that comint-password-prompt-regexp does not translate
> "for" into other languages ("para" in this case).
next prev parent reply other threads:[~2017-03-01 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 1:48 bug#25596: 25.1; Password not hidden Rahul Martim Juliato
2017-02-01 17:48 ` Glenn Morris
2017-02-02 20:53 ` Rahul Martim Juliato
2017-02-23 22:00 ` Glenn Morris
2017-03-01 17:27 ` Rahul Martim Juliato [this message]
2017-04-28 20:19 ` 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=86h93c6h70.fsf@gmail.com \
--to=rahuljuliato@gmail.com \
--cc=25596@debbugs.gnu.org \
--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).