all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: wxhgmqzgwmuf@spammotel.com, emacs-orgmode@gnu.org
Subject: Re: Enriched/Org is a colorful Org
Date: Thu, 11 Apr 2013 20:30:10 +0300	[thread overview]
Message-ID: <83vc7t9dr1.fsf@gnu.org> (raw)
In-Reply-To: <DC3DE7E9-91DB-4F5E-A094-836E8DC9A6FB@gmail.com>

> From: Carsten Dominik <carsten.dominik@gmail.com>
> Date: Thu, 11 Apr 2013 04:58:15 +0200
> Cc: "emacs-orgmode@gnu.org List" <emacs-orgmode@gnu.org>,
>  Eli Zaretskii <eliz@gnu.org>
> 
> > I guess Eli simply means, in a general way, that overlays do negatively impact
> > display performance, as you said as well a couple of times:
> 
> Yes, but Eli says that Org already severely tests the
> display engine, and he uses the word "mess", even though
> we mostly use text properties for faces and other
> display-related things.

Well, don't interpret "mess" too literally ;-)

> Of course, Org already uses overlays, for example for
> folding (as does outline.el), and for temporary marking
> of text like during src block editing.  But as your digging
> shows, I ave avoided them in the past, and we are also not
> using them for org-indent.el, for example.
> 
> The reason why I said "overlays would be better" is simply
> that they would allow to add display properties in a
> persistent way that would not interfere that our
> font-lock-unfontify-region function removes face and
> invisibility text properties.  So they are "better" for
> implementing hand-made faces selection that should overrule
> font-lock.

Overlays should be OK as long as they aren't too many, and as long as
you don't move them around too much, particularly in post-command-hook
or some such.

  reply	other threads:[~2013-04-11 17:29 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10  4:02 Enriched/Org is a colorful Org Jambunathan K
2013-04-10  9:54 ` Suvayu Ali
2013-04-10 10:16   ` Carsten Dominik
2013-04-10 10:39     ` Torsten Wagner
2013-04-10 10:48     ` Suvayu Ali
2013-04-10 10:53       ` Carsten Dominik
2013-04-10 11:20         ` Sebastien Vauban
2013-04-10 11:26           ` Carsten Dominik
2013-04-10 12:15           ` Jambunathan K
2013-04-10 11:57     ` Jambunathan K
2013-04-10 16:21     ` Eli Zaretskii
2013-04-10 16:43       ` Jambunathan K
2013-04-10 17:13         ` Eli Zaretskii
2013-04-10 19:58       ` Carsten Dominik
2013-04-10 20:16         ` Sebastien Vauban
2013-04-11  2:58           ` Carsten Dominik
2013-04-11 17:30             ` Eli Zaretskii [this message]
2013-04-11 22:49               ` Carsten Dominik
2013-04-12  6:41                 ` Eli Zaretskii
2013-04-12  7:13                   ` Carsten Dominik
2013-04-12  8:31                     ` Eli Zaretskii
2013-04-12 10:56                       ` Carsten Dominik
2013-04-12 11:49                         ` Torsten Wagner
2013-04-12 13:03                           ` Eli Zaretskii
2013-04-12 18:00                             ` Suvayu Ali
2013-04-12 18:38                               ` Eli Zaretskii
2013-04-13 10:50                                 ` Suvayu Ali
2013-04-12 12:36                         ` Eli Zaretskii
2013-04-13 12:24                           ` Sean O'Halpin
2013-04-13 14:38                             ` Jambunathan K
2013-04-13 15:01                             ` Eli Zaretskii
2013-04-12  8:35                     ` Bastien
2013-04-12 14:45                       ` François Pinard
2013-04-18 20:37                         ` Samuel Wales
2013-04-11 17:27         ` Eli Zaretskii
2013-04-11 22:46           ` Carsten Dominik
2013-04-10 12:12   ` Jambunathan K

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=83vc7t9dr1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=wxhgmqzgwmuf@spammotel.com \
    /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.