From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 9159@debbugs.gnu.org
Subject: bug#9159: 24.0.50; `undo' is not as good as it should be wrt property changes
Date: Tue, 2 Aug 2011 13:48:03 -0700 [thread overview]
Message-ID: <D57431400FFD46D5A372207627257ABD@us.oracle.com> (raw)
In-Reply-To: <jwvpqkneirn.fsf-monnier+emacs@gnu.org>
> >> > C-M-_ to undo the last change.
> >> > With point in the same place, do `C-u C-x ='.
> >> > That shows that there is property `foo' there, with value nil.
> >>
> >> Do you have an example situation where the difference matters?
> >
> > What does "matters" mean?
>
> By "matters" I mean that the difference is reflected in a different
> behavior for "the end user". I'm sure you know what I mean.
I _described_ a visible difference for the end user. That is pretty much the
only things I care about in general: user-visible behavior.
What is not user-visible in the behavior I reported? The whole point of the
report was about the behavior being confusing to an end user.
> > Evidently it does not matter much to you.
>
> Not until I see that it has some more serious consequence. What you
> show is a mostly cosmetic difference.
Call it such a name if that makes you feel better.
It is a user-visible difference that promotes confusion.
No, it is not the most important problem Emacs has.
And it is unlikely to cause mass destruction.
> >> Usually we handle the absence of a text property as
> >> synonym to a nil value of that property.
> >
> > Yes, I know that. And this is a good example where it makes
> > a difference.
A user-visible difference, I might have added.
> If you accept the fact that "nothing == nil" for text-properties, then
> the difference you show is indeed not a difference, it's just
> a cosmetically different way to represent the same state.
Whatever. If you don't think this difference in what the user sees and what
s?he is likely to expect/understand promotes confusion, or if you see it but
don't care, nothing I say will change your mind.
I already said in the OP that "while correct" (N.B.) "it would be better for the
property `foo' to simply be removed."
We agree that the value shown is correct. I say that although correct it is
confusing. You say that it's just cosmetic - bad looks. Your poor cosmetics
can confuse users. And that was the point, from the beginning.
next prev parent reply other threads:[~2011-08-02 20:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 2:06 bug#9159: 24.0.50; `undo' is not as good as it should be wrt property changes Drew Adams
2011-08-02 4:16 ` Stefan Monnier
2011-08-02 17:34 ` Drew Adams
2011-08-02 19:10 ` Stefan Monnier
2011-08-02 20:48 ` Drew Adams [this message]
2011-08-02 21:13 ` Lars Magne Ingebrigtsen
2011-08-02 21:48 ` Drew Adams
2011-09-11 2:36 ` Lars Magne Ingebrigtsen
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=D57431400FFD46D5A372207627257ABD@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=9159@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).