unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to fontify region according to mode
Date: Sat, 14 Aug 2010 20:35:48 +0200	[thread overview]
Message-ID: <AANLkTik7v4uoEkiONX-Bp8dk+FRvYtEJFQL7n6XE0Xu2@mail.gmail.com> (raw)
In-Reply-To: <874oexdq3f.fsf@stats.ox.ac.uk>

On Sat, Aug 14, 2010 at 8:08 PM, Dan Davison <davison@stats.ox.ac.uk> wrote:
> Lennart Borgman <lennart.borgman@gmail.com> writes:
>
>> On Sat, Aug 14, 2010 at 7:14 PM, Dan Davison <davison@stats.ox.ac.uk> wrote:
>>> I want to write a function to fontify a region according to a certain
>>> mode, and I tried the following tactic (see function below):
>>>
>>> - get the value of `font-lock-defaults' from a buffer in the target mode
>>>  and bind it inside a let
>>> - bind a bunch of other font-lock variable names to stop them being
>>>  overwritten
>>> - call `font-lock-set-defaults'
>>> - call `font-lock-fontify-region'
>>>
>>> It didn't seem to work. Could someone suggest how to alter this so that
>>> it works, or is this approach fundamentally flawed?
>>>
>>> (defun dan/font-lock-fontify-region (mode start end)
>>>  (let ((font-lock-defaults
>>>         (with-temp-buffer
>>>           (funcall mode)
>>>           font-lock-defaults))
>>>        font-lock-keywords
>>>        font-lock-keywords-only
>>>        font-lock-keywords-case-fold-search
>>>        font-lock-syntax-table
>>>        font-lock-beginning-of-syntax-function)
>>>    (font-lock-set-defaults)
>>>    (font-lock-fontify-region start end)))
>>>
>>>
>>> I want the rest of the buffer to remain unaltered and, for now, I'm not
>>> looking for a solution involving mumamo/multi-mode etc.
>>
>>
>> If you want to see how it works then look in mumamo.el. I think you
>> will find the answers to your questions there. (But why do you want to
>> reinvent the wheel? What is the purpose?)
>
> Hi Lennart,
>
> I was looking at mumamo.el earlier today, but it is 9,101 lines long, so
> I would definitely appreciate some guidance. Note that I don't want
> different regions to be subject to different major modes; I only want to
> change the text properties in a region. That was why I was not using
> mumamo and was attempting the simple approach above. I would certainly
> consider mumamo if I wanted multiple major modes.
>
> Dan


Hi Dan,

I am afraid that what you want actually involves the same problem as
using multiple major modes. Why don't you think so?



  reply	other threads:[~2010-08-14 18:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-14 17:14 How to fontify region according to mode Dan Davison
2010-08-14 17:21 ` Lennart Borgman
2010-08-14 18:08   ` Dan Davison
2010-08-14 18:35     ` Lennart Borgman [this message]
2010-08-16 13:28       ` Dan Davison
2010-08-16 14:39         ` Lennart Borgman

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=AANLkTik7v4uoEkiONX-Bp8dk+FRvYtEJFQL7n6XE0Xu2@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=davison@stats.ox.ac.uk \
    --cc=help-gnu-emacs@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.
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).