From: Richard Stallman <rms@gnu.org>
Cc: jet@gyve.org, miles@lsi.nec.co.jp, miles@gnu.org, emacs-devel@gnu.org
Subject: Re: Behavior of evaporate
Date: Fri, 26 Sep 2003 22:31:59 -0400 [thread overview]
Message-ID: <E1A34sJ-00059d-Kx@fencepost.gnu.org> (raw)
In-Reply-To: <x54qyzdi3f.fsf@lola.goethe.zz> (message from David Kastrup on 26 Sep 2003 11:17:24 +0200)
Yes. From the manual:
`evaporate'
If this property is non-`nil', the overlay is deleted automatically
if it ever becomes empty (i.e., if it spans no characters).
But the overlay does not become empty in your example. It _is_
already empty.
I clarified the manual as follows:
@item evaporate
@kindex evaporate @r{(overlay property)}
If this property is non-@code{nil}, the overlay is deleted automatically
if it becomes empty (i.e., if its length becomes zero). However,
if the overlay is @emph{already} empty, @code{evaporate} does not
delete it.
Is that entirely correct?
Also, is that really what we want? Maybe setting the `evaporate'
property non-nil should delete the overlay immediately if it is
already empty. That would be more consistent.
next prev parent reply other threads:[~2003-09-27 2:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 12:16 popup menu support for smerge-mode Masatake YAMATO
2003-01-11 19:41 ` Stefan Monnier
2003-08-24 6:03 ` Masatake YAMATO
2003-08-24 14:42 ` Stefan Monnier
2003-09-18 8:54 ` Masatake YAMATO
2003-09-18 15:27 ` Stefan Monnier
2003-09-19 9:25 ` Masatake YAMATO
2003-09-19 15:57 ` Stefan Monnier
2003-09-26 7:58 ` Masatake YAMATO
2003-09-26 8:44 ` Miles Bader
2003-09-26 8:53 ` Behavior of evaporate Masatake YAMATO
2003-09-26 9:05 ` Miles Bader
2003-09-26 9:17 ` David Kastrup
2003-09-26 15:59 ` Stefan Monnier
2003-09-27 2:31 ` Richard Stallman [this message]
2003-09-30 20:56 ` Alex Schroeder
2003-10-20 21:23 ` popup menu support for smerge-mode Stefan Monnier
2004-03-10 4:32 ` Masatake YAMATO
2004-03-11 7:00 ` Masatake YAMATO
2003-10-14 3:59 ` Masatake YAMATO
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1A34sJ-00059d-Kx@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jet@gyve.org \
--cc=miles@gnu.org \
--cc=miles@lsi.nec.co.jp \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.