unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: tex-mode.el
Date: Thu, 11 Feb 2021 05:01:08 +0100	[thread overview]
Message-ID: <trinity-c496ee77-a1b0-4a16-8d81-175baeb65fd6-1613016068759@3c-app-mailcom-bs12> (raw)
In-Reply-To: <87a6sbxob4.fsf@web.de>

When I used "tex-mode.el", the suscript fontification can be disabled
using the following function.  But does not work with my minor-mode.

(defun supinf-disable ()
   (interactive)
   (setq-local tex-fontify-script nil)
   (font-lock-flush))

I am trying to have two functions, one to enable, another
to disable.  Enabling is also creating me problems to set up.
The code in tex-mode.el is in quite a mess and surely does not
help a lot.

> Sent: Thursday, February 11, 2021 at 3:42 PM
> From: "Michael Heerdegen" <michael_heerdegen@web.de>
> To: help-gnu-emacs@gnu.org
> Subject: Re: tex-mode.el
>
> Christopher,
>
> After commenting out the `multic' expression I could try your example.
>
> I'm not really skilled with font-lock.
>
> I think in your case `font-lock-flush' is indeed not enough, I think
> that one doesn't unfontify, which has to be done in your case.
> `font-lock-refresh-defaults' as had been suggested should be better.
>
> Your unfontify function seems to work when called (tested).  But is it
> called?
>
> I think here:
>
> (defun supinf-disable ()
>   "Disable the supinf typeface"
>   (font-lock-flush (point-min) (point-max))
>   (setq font-lock-defaults
> 	'(font-lock-unfontify-region-function . supinf-disable-cruc))
>         ^^^^
>   ;;(supinf-disable-cruc (point-min) (point-max))
>   (font-lock-flush (point-min) (point-max)) )

Yes, it was a bad attempt from my part.  It was the routine hack I was
playing with.

> you are missing a level of parens.  Then, with some good will, the thing
> could indeed work I think.
>
> Oh, and it seems something in your mode is not done buffer locally,
> since the ^^^^ underlining here now looks weird in my messages buffer,
> where I definitely didn't enable your mode.  Or maybe just a side effect
> of experimenting, dunno.
>
> HTH,
>
> Michael.
>
>
>



  reply	other threads:[~2021-02-11  4:01 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09 17:13 tex-mode.el Christopher Dimech
2021-02-09 17:22 ` tex-mode.el Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-09 17:45   ` tex-mode.el Christopher Dimech
2021-02-09 18:15     ` tex-mode.el Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-09 18:26       ` tex-mode.el Christopher Dimech
2021-02-09 18:37         ` tex-mode.el Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-09 18:52           ` tex-mode.el Christopher Dimech
2021-02-09 19:05             ` tex-mode.el Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-09 19:39               ` tex-mode.el Christopher Dimech
2021-02-09 19:45               ` tex-mode.el Christopher Dimech
2021-02-10 20:43               ` tex-mode.el Christopher Dimech
2021-02-10 20:49                 ` tex-mode.el Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-10 21:01                   ` tex-mode.el Christopher Dimech
2021-02-10 21:21                     ` tex-mode.el Stefan Monnier
2021-02-10 21:25                       ` tex-mode.el Christopher Dimech
2021-02-10 21:30                         ` tex-mode.el Stefan Monnier
2021-02-10 21:54                           ` tex-mode.el Christopher Dimech
2021-02-11  3:13                     ` tex-mode.el Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-11  3:27                       ` tex-mode.el Christopher Dimech
2021-02-09 20:13         ` tex-mode.el tomas
2021-02-09 20:26           ` tex-mode.el Christopher Dimech
2021-02-09 20:45             ` tex-mode.el tomas
2021-02-10  3:53               ` tex-mode.el Michael Heerdegen
2021-02-10  4:01                 ` tex-mode.el Christopher Dimech
2021-02-11  3:42                   ` tex-mode.el Michael Heerdegen
2021-02-11  4:01                     ` Christopher Dimech [this message]
2021-02-11  4:11                       ` tex-mode.el Michael Heerdegen
2021-02-11  4:27                         ` tex-mode.el Christopher Dimech
2021-02-11 13:29                         ` tex-mode.el Christopher Dimech
2021-02-11 21:11                   ` tex-mode.el Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-11 23:08                     ` tex-mode.el Christopher Dimech

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=trinity-c496ee77-a1b0-4a16-8d81-175baeb65fd6-1613016068759@3c-app-mailcom-bs12 \
    --to=dimech@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).