From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30186@debbugs.gnu.org, juri@linkov.net
Subject: bug#30186: 27.0.50; Password is not hidden in read-passwd
Date: Fri, 26 Jan 2018 20:00:27 +0000 [thread overview]
Message-ID: <20180126200027.GB5056@ACM> (raw)
In-Reply-To: <831sicl9p3.fsf@gnu.org>
Good evening, Eli.
On Fri, Jan 26, 2018 at 21:08:24 +0200, Eli Zaretskii wrote:
> > Date: Fri, 26 Jan 2018 18:37:02 +0000
> > From: Alan Mackenzie <acm@muc.de>
> > Cc: 30186@debbugs.gnu.org
> > The problem here appears to be a fundamental design bug in Emacs: that
> > text properties are regarded as part of the buffer rather than something
> > accompanying the buffer, as overlays are.
> It's not a bug, it's a feature (and a very important one).
Yes. We see its utility in read-passwd. But don't worry, I wasn't
proposing to "fix" it. :-)
Do you have any opinion on my suggestion:
> > Perhaps an alternative would be for Emacs to provide a flag which
> > indicates to a before/after-change-function whether the current
> > change is a "proper" change or merely a text property change.
> > Change hook functions could then test this flag and, for example,
> > refrain from doing anything for a text property change.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2018-01-26 20:00 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
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 [this message]
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=20180126200027.GB5056@ACM \
--to=acm@muc.de \
--cc=30186@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.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 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).