unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: moasenwood@zoho.eu
Cc: help-gnu-emacs@gnu.org
Subject: Re: tex-mode.el
Date: Tue, 9 Feb 2021 19:52:41 +0100	[thread overview]
Message-ID: <trinity-846b1618-c51a-4fc7-a6d9-c6eb91e2c4e9-1612896761312@3c-app-mailcom-bs05> (raw)
In-Reply-To: <8735y5jde6.fsf@zoho.eu>


> Sent: Wednesday, February 10, 2021 at 6:37 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:
>
> > tex-font-lock-match-suscript matches superscripts (matching
> > part following ^) and subscripts (matching part following
> > _). An example is "\alpha^i" and "\beta_j".
>
> OK, one step at a time, As you see from the source, that
> function doesn't do anything if you set `tex-fontify-script'
> to nil.
>
>   (setq tex-fontify-script nil)
>
> Now what happens?

It does nothing but stops matching superscript and subscript.
And I am not sure "tex-font-lock-unfontify-region" does anything
either.

> --
> underground experts united
> http://user.it.uu.se/~embe8573
> https://dataswamp.org/~incal
>
>
>



  reply	other threads:[~2021-02-09 18:52 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           ` Christopher Dimech [this message]
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                     ` 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-846b1618-c51a-4fc7-a6d9-c6eb91e2c4e9-1612896761312@3c-app-mailcom-bs05 \
    --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).