From: Carsten Dominik <dominik@science.uva.nl>
To: Eddward DeVilla <eddward@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: radio transmit links across files
Date: Thu, 8 Mar 2007 10:48:07 +0100 [thread overview]
Message-ID: <417f6f09a543129abed8b51e3242d69b@science.uva.nl> (raw)
In-Reply-To: <b71b18520703070712n58862efeq4787397bb0aa4201@mail.gmail.com>
On Mar 7, 2007, at 16:12, Eddward DeVilla wrote:
> On 3/7/07, Carsten Dominik <dominik@science.uva.nl> wrote:
>> The main problem with such an approach is that it quickly becomes
>> a performance issue. It is ok for a few terms, but if you accumulate
>> a large number of terms, and if you want to use font-lock to activate
>> words as links, this means that after each letter you type, font-lock
>> will have to match all words in the current line against all those
>> terms.
>> This can become slow.
>
> Hi. A question from the peanut gallery. Could the checking to see if
> a term matches be deferred until the user types a non-whitespace
> character followed by either a whitespace character or a movement
> operation? If this is possible, it might speed things up a little. I
> don't know enough about how font-lock work to know if this reasonable.
I don't think you can do this in font-lock. Font-lock has many clever
mechanisms to defer font-locking of stuff that is not currently on the
screen
etc, but the current line is always done immediately, I think.
The problem with your proposal is also that you may be inserting or
deleting characters in the middle of a word, and a whitespace-based
approach would not work then.
- Carsten
next prev parent reply other threads:[~2007-03-08 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 11:52 radio transmit links across files Mark Aufflick
2007-03-07 8:04 ` Carsten Dominik
2007-03-07 15:12 ` Eddward DeVilla
2007-03-08 9:48 ` Carsten Dominik [this message]
2007-03-08 16:39 ` Eddward DeVilla
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=417f6f09a543129abed8b51e3242d69b@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=eddward@gmail.com \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).