unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: martin rudalics <rudalics@gmx.at>
Cc: 30186@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#30186: 27.0.50; Password is not hidden in read-passwd
Date: Sat, 27 Jan 2018 09:21:24 +0000	[thread overview]
Message-ID: <20180127092124.GA4049@ACM> (raw)
In-Reply-To: <5A6C3802.1050603@gmx.at>

Hello, Martin.

On Sat, Jan 27, 2018 at 09:27:46 +0100, martin rudalics wrote:
>  > 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.

> Is that interpretation correct?

No.  I'm half joking.  But an awful lot of Lisp code runs an awful lot of
code separating text properties from actual text, mainly by preventing
the change hooks being run for text property changes.

read-passwd is an example (the only one I know) of the change hooks being
an essential part of text property manipulation.

> I always regard text properties part of some text (as they are retained
> when copying text from one buffer to another) and only their text part
> of the buffer.  And I do regard overlays parts of their buffers.  Am I
> wrong?

Text properties are indeed part of the buffer (or string).  But I don't
think overlays are - if you have an overlay on part of a buffer, and copy
that part into a string, I don't think the overlay stays on the copy.

> martin

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2018-01-27  9:21 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
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 [this message]
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=20180127092124.GA4049@ACM \
    --to=acm@muc.de \
    --cc=30186@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=rudalics@gmx.at \
    /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).