unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Aurel Buche <au.buchet@gmail.com>
To: emacs-devel@gnu.org
Subject: font-lock-mode limitations
Date: Tue, 19 Mar 2019 17:11:02 +0000	[thread overview]
Message-ID: <CAGQ2GfoUwN28jdT7tt60xf4e8oa800niHSrVa1W+xo+S=eQPJA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]

Hi,

I am working for a company that uses a proprietary Scheme based language
The language has a rich API and its own conventions, so I created a new
major mode but I am struggling with fontification:

I have elisp functions to fetch all documented functions and user-defined
functions from my code and add them properly to font-lock-defaults (using
regexp-opt)

Everything was working fine while I was fetching keywords from a very
limited number of modules. But now I am using more of them and I have
hundreds (maybe thousands) of keywords to highlights. Now that I added more
functions to font-lock-defaults nothing is highlighted anymore.

I really need to add those modules and I definitely require fontification
as I am too used to it.
I don't want to replace keywords with more global regular expressions as it
is really helpful to have keywords highlighted only when they are written
properly

I took a quick glimpse at font-core.el and font-lock.el but I could not
find where the regexp match limitations are set

Do you have a solution or an idea to increase the limits of keywords that
can be matched by font-lock-mode ?

I would be extremely grateful if you can help me

Regards,

Aurélien Buchet

[-- Attachment #2: Type: text/html, Size: 1836 bytes --]

             reply	other threads:[~2019-03-19 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 17:11 Aurel Buche [this message]
2019-03-19 18:48 ` font-lock-mode limitations 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='CAGQ2GfoUwN28jdT7tt60xf4e8oa800niHSrVa1W+xo+S=eQPJA@mail.gmail.com' \
    --to=au.buchet@gmail.com \
    --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 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).