all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: emacs-devel@gnu.org
Subject: Re: hi-lock and overlays
Date: Wed, 20 Jan 2010 18:19:48 +0100	[thread overview]
Message-ID: <87y6js66dn.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <jwvvdewojqn.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 20 Jan 2010 10:54:47 -0500")

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

>>   - Why does hi-lock use two different styles of highlighting?  IMO, if
>>     a user does M-x highlight-regexp RET foo RET hi-yellow RET, he
>>     expects to get that highlighting even if there are other overlays,
>>     so creating an overlay (and maybe even setting a priority) is the
>>     only safe bet.
>
> overlays are implemented inefficiently, so if you have many of them,
> redisplay, buffer modifications, and other operations can become
> noticeably slower.

I see, but still I think that deciding between font-lock and overlays by
the value of `font-lock-fontified' is weird, and I'd vote for an
optional parameter that lets one specify the method to be used
explicitly.  What do yau think?

Ok, back to the original problem that hl-line-mode's overlay supresses
the font-lock highlighting added by hi-lock.  The cleanest solution
seems to be to decide on the usage of negative overlay priorities to
make font-lock take precedence here, and hl-line-mode's overlay would
use one.  But I don't know how feasible that is.

Bye,
Tassilo




      reply	other threads:[~2010-01-20 17:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-17 18:04 Conflicting overlays and the 'priority property Tassilo Horn
2010-01-18 21:33 ` hi-lock and overlays (was: Conflicting overlays and the 'priority property) Tassilo Horn
2010-01-18 21:51   ` Lennart Borgman
2010-01-19  7:41     ` hi-lock and overlays Tassilo Horn
2010-01-20 15:54   ` Stefan Monnier
2010-01-20 17:19     ` Tassilo Horn [this message]

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=87y6js66dn.fsf@thinkpad.tsdh.de \
    --to=tassilo@member.fsf.org \
    --cc=emacs-devel@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.