From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30186@debbugs.gnu.org
Subject: bug#30186: 27.0.50; Password is not hidden in read-passwd
Date: Sun, 21 Jan 2018 23:19:39 +0200 [thread overview]
Message-ID: <87bmhm7wbw.fsf@mail.linkov.net> (raw)
In-Reply-To: <83zi57qk2w.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 21 Jan 2018 17:59:19 +0200")
>> This can be traced down to ‘remove-yank-excluded-properties’
>> where ‘set-text-properties’ used to leave ‘display’ properties
>> (with ‘.’ over inserted characters) in the minibuffer.
>
> Can you spot the commit which causes this, or bisect to find it?
I'm trying to find a relevant commit in the git log manually
because bisect is not feasible for me - ‘make’ takes more than
one hour to recompile. Is there a service like Travis CI that
could do bisect and compile its commits and check for exit codes
of the provided script containing the required condition?
next prev parent reply other threads:[~2018-01-21 21:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 21:29 bug#30186: 27.0.50; Password is not hidden in read-passwd Juri Linkov
2018-01-21 15:59 ` Eli Zaretskii
2018-01-21 21:19 ` Juri Linkov [this message]
2018-01-22 18:27 ` Glenn Morris
2018-01-22 18:45 ` Glenn Morris
2018-01-22 21:38 ` Juri Linkov
2018-01-23 21:38 ` Juri Linkov
2018-01-25 17:39 ` Alan Mackenzie
2018-01-25 21:15 ` Juri Linkov
2018-01-26 18:37 ` Alan Mackenzie
2018-01-26 19:08 ` Eli Zaretskii
2018-01-26 20:00 ` Alan Mackenzie
2018-01-27 9:40 ` Eli Zaretskii
2018-01-27 11:37 ` Alan Mackenzie
2018-01-27 12:23 ` Eli Zaretskii
2018-01-27 13:38 ` Alan Mackenzie
2018-01-27 21:43 ` Juri Linkov
2018-01-27 22:10 ` Alan Mackenzie
2018-01-27 8:27 ` martin rudalics
2018-01-27 9:21 ` Alan Mackenzie
2018-01-30 8:30 ` martin rudalics
2018-01-22 1:53 ` 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=87bmhm7wbw.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=30186@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).