From: Christopher Dimech <dimech@gmx.com>
To: moasenwood@zoho.eu
Cc: help-gnu-emacs@gnu.org
Subject: Re: tex-mode.el
Date: Wed, 10 Feb 2021 22:01:04 +0100 [thread overview]
Message-ID: <trinity-6685a255-e725-4882-b26c-b7ac5b77b1e6-1612990864947@3c-app-mailcom-bs12> (raw)
In-Reply-To: <871rdnfy2i.fsf@zoho.eu>
> Sent: Thursday, February 11, 2021 at 8:49 AM
> From: "Emanuel Berg via Users list for the GNU Emacs text editor" <help-gnu-emacs@gnu.org>
> To: help-gnu-emacs@gnu.org
> Subject: Re: tex-mode.el
>
> Christopher Dimech wrote:
>
> > This disabling thing for tex-mode is killing me.
>
> Well, why is it so important? Try to think of/do something
> else...
I did not think it would be so difficult to do.
> But, did you Tassilo Horn's suggestion?
>
> (defun th/tex-toggle-script ()
> (interactive)
> (setq-local tex-fontify-script (not tex-fontify-script))
> (font-lock-flush))
> What happens?
Still same problem
(setq-local tex-fontify-script nil)
(font-lock-flush)
It works in the sense that when I call it the new text is not
fontified. However, the text that was already fontified remains
fontified.
> --
> underground experts united
> http://user.it.uu.se/~embe8573
> https://dataswamp.org/~incal
>
>
>
next prev parent reply other threads:[~2021-02-10 21: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 ` Christopher Dimech [this message]
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 ` tex-mode.el Christopher Dimech
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-6685a255-e725-4882-b26c-b7ac5b77b1e6-1612990864947@3c-app-mailcom-bs12 \
--to=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).