unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, miles@gnu.org
Subject: Re: Combining face and map stuff
Date: Wed, 06 Oct 2010 05:57:59 +0200	[thread overview]
Message-ID: <83y6acnfaw.fsf@gnu.org> (raw)
In-Reply-To: <jwvzkusqkn7.fsf-monnier+emacs@gnu.org>

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
> Date: Wed, 06 Oct 2010 01:43:03 +0200
> 
> >>> It sounds like he's saying it would use their union, with a
> >>> property-specific function used to compute that union.
> >>> [and that the union computation could be done at "property setting time"
> >>> rather than at display time, to avoid speed problems.]
> >> I'm probably missing something here: if the union is computed at
> >> put-text-property time, then how is this different from what we have
> >> now?  That union will have all the properties of the character lumped
> >> together, just like what we have now, right?  What am I missing?
> 
> You're missing that in order o properly update the merge when some
> property is added/removed in a plane, all users of text properties will
> have to follow some new conventions.

When I said "what am I missing", I meant the advantages of what you
propose.  Having to follow some new conventions sounds like the price
one has to pay for having these advantages, but what are the
advantages themselves?

If the new protocol itself is the advantage, then perhaps what I'm
missing is the essence of the problems that you proposal is trying to
solve.



  reply	other threads:[~2010-10-06  3:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-02 14:21 Combining face and map stuff Lars Magne Ingebrigtsen
2010-10-02 16:21 ` Chong Yidong
2010-10-02 16:41   ` Lars Magne Ingebrigtsen
2010-10-03  2:04     ` Miles Bader
2010-10-03  4:16     ` Chong Yidong
2010-10-03 13:08       ` Lars Magne Ingebrigtsen
2010-10-03 23:37 ` Stefan Monnier
2010-10-04  7:56   ` Eli Zaretskii
2010-10-04  9:03     ` Miles Bader
2010-10-04  9:42       ` Eli Zaretskii
2010-10-05  0:12         ` Miles Bader
2010-10-05 23:43           ` Stefan Monnier
2010-10-06  3:57             ` Eli Zaretskii [this message]
2010-10-07  7:40               ` Stefan Monnier
2010-10-07 13:56                 ` Eli Zaretskii
2010-10-07 18:08                   ` Stefan Monnier
2010-10-12 19:09                     ` Eli Zaretskii
2010-10-12 20:23                       ` Stefan Monnier
2010-10-13 11:41                         ` Eli Zaretskii
2010-10-13 12:42                           ` Stefan Monnier

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=83y6acnfaw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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).