From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>,
Richard Stallman <rms@gnu.org>,
David.Kastrup@t-online.de, emacs-devel@gnu.org
Subject: Re: Should invisible imply intangible?
Date: Fri, 15 Mar 2002 19:59:08 -0500 [thread overview]
Message-ID: <200203160059.g2G0x8F04836@rum.cs.yale.edu> (raw)
In-Reply-To: 87d6y5mita.fsf@tc-1-100.kawasaki.gol.ne.jp
> "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu> writes:
> > I'm not completely sure about that. After all, why would someone
> > put a `display' property on an `invisible' overlay if the `invisible'
> > property means that the `display' property will be ignored anyway ?
>
> Perhaps the properties come from different sources (e.g., one form a
> text property, one from an overlay)?
I was specifically referring to the case where both properties come
from the same overlay. I don't know what should (or does) happen
when the two properties come from different sources.
Stefan
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-03-16 0:59 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-23 20:19 Should invisible imply intangible? Richard Stallman
2002-02-23 21:24 ` Paul Michael Reilly
2002-02-25 0:09 ` Richard Stallman
2002-02-25 5:10 ` Stefan Monnier
2002-02-26 20:13 ` Richard Stallman
2002-03-01 1:30 ` Stefan Monnier
2002-03-03 14:40 ` Richard Stallman
2002-03-03 17:11 ` Stefan Monnier
2002-03-04 23:41 ` Richard Stallman
2002-03-04 23:46 ` Stefan Monnier
2002-03-05 1:40 ` Stefan Monnier
2002-03-07 2:30 ` Richard Stallman
2002-03-04 23:41 ` Richard Stallman
2002-03-05 21:58 ` Richard Stallman
2002-03-05 23:04 ` Stefan Monnier
2002-03-05 23:34 ` Stefan Monnier
2002-03-09 20:03 ` Richard Stallman
2002-03-09 22:37 ` Stefan Monnier
2002-03-10 21:32 ` Richard Stallman
[not found] ` <200203102202.g2AM26q06798@rum.cs.yale.edu>
2002-03-11 19:06 ` Richard Stallman
2002-03-12 17:56 ` Stefan Monnier
2002-03-13 10:58 ` Richard Stallman
2002-03-13 11:19 ` David Kastrup
2002-03-15 3:41 ` Richard Stallman
2002-03-15 11:47 ` David Kastrup
2002-03-16 6:39 ` Richard Stallman
2002-03-16 11:58 ` David Kastrup
2002-03-18 9:06 ` Richard Stallman
2002-03-18 23:36 ` David Kastrup
2002-03-19 7:24 ` Eli Zaretskii
2002-03-19 11:12 ` David Kastrup
2002-03-16 0:22 ` Stefan Monnier
2002-03-16 0:56 ` Miles Bader
2002-03-16 0:59 ` Stefan Monnier [this message]
2002-03-16 1:25 ` David Kastrup
2002-03-17 10:06 ` Richard Stallman
2002-03-16 1:18 ` David Kastrup
2002-03-16 1:28 ` Stefan Monnier
2002-03-16 2:16 ` David Kastrup
2002-03-16 3:29 ` Miles Bader
2002-03-16 4:05 ` David Kastrup
2002-03-23 23:37 ` David Kastrup
2002-03-13 13:06 ` Stefan Monnier
2002-03-13 14:15 ` David Kastrup
2002-03-13 16:53 ` Stefan Monnier
2002-03-14 12:42 ` Richard Stallman
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=200203160059.g2G0x8F04836@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=David.Kastrup@t-online.de \
--cc=emacs-devel@gnu.org \
--cc=rms@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 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.