unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: 14157@debbugs.gnu.org
Subject: bug#14157: 24.3.50; Improve facemenu.el: Better "integration" with other libraries
Date: Wed, 10 Apr 2013 19:49:20 +0300	[thread overview]
Message-ID: <837gka9vqn.fsf@gnu.org> (raw)
In-Reply-To: <8761zubb8o.fsf@gmail.com>

> From: Jambunathan K <kjambunathan@gmail.com>
> Cc: 14157@debbugs.gnu.org
> Date: Wed, 10 Apr 2013 21:59:11 +0530
> 
> When in an Org file, I want enriched mode to be turned on and the
> highlighted text to be persisted in the saved Org file.

Enriched mode is a means to an end.  But it's not the only means.

What you need is a way to tell Org to re-highlight some parts of the
text when the file is revisited.  How hard can that be?

> As I indicated the blocker is that facemenu.el doesn't play nicely with
> font-lock-modes.

No face plays nicely with font-lock-modes.

> Do you think that it is possible to achieve what users are requesting
> without using overlays?

Of course.

> As for Orgmode straining the display engine, it depends on many factors
> - I guess the size of the Orgmode file, number of foldings, number of
> overlays etc.

The problem is that a typical Org file has a lot of all of those.
Just moving vertically through a single display line might mean moving
hundreds of KBytes in the buffer.  The way Emacs display was designed,
this use case was not considered as an important one.

> I have seen prior discussions of using augmented interval trees for
> managing overlays.  (Theoretically) Will such a migration alleviate the
> problem/fear.

Being able to find overlays efficiently is only one part of the
problem.  The other one is that we have no easy way of finding which
parts of the buffer are "covered" by an overlay.  That forces many
dubious and expensive tricks during redisplay.





  reply	other threads:[~2013-04-10 16:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08  5:52 bug#14157: 24.3.50; Improve facemenu.el: Better "integration" with other libraries Jambunathan K
2013-04-10  3:50 ` Jambunathan K
2013-04-10 15:58   ` Eli Zaretskii
2013-04-10 16:29     ` Jambunathan K
2013-04-10 16:49       ` Eli Zaretskii [this message]
2013-04-10 17:48       ` Stefan Monnier
2013-04-11  4:39         ` Jambunathan K
2013-04-10 17:45     ` Stefan Monnier
2013-04-10 16:14   ` Eli Zaretskii
2013-04-10 16:34     ` Jambunathan K
2013-04-10 16:43       ` Eli Zaretskii
2013-11-15  4:47 ` 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

  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=837gka9vqn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=14157@debbugs.gnu.org \
    --cc=kjambunathan@gmail.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 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).