unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Lack of command highlighting in texinfo-mode
Date: Fri, 7 May 2021 08:19:36 +0200	[thread overview]
Message-ID: <trinity-60ad2602-a289-4dc9-9d39-c7a64d22ab9d-1620368375980@3c-app-mailcom-bs12> (raw)
In-Reply-To: <83k0obcbw3.fsf@gnu.org>


Yes, but why don't we change texinfo.tex so there will be some good highlighting
by default.

---------------------
Christopher Dimech
General Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy


> Sent: Friday, May 07, 2021 at 6:10 PM
> From: "Eli Zaretskii" <eliz@gnu.org>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Lack of command highlighting in texinfo-mode
>
> > From: Christopher Dimech <dimech@gmx.com>
> > Date: Fri, 7 May 2021 01:08:23 +0200
> >
> >
> > What code takes care of texinfo highlighting for the following
> > Contents in @anchor do get highlighted, but there is no highlighting
> > for most of the others by default.  This makes code very difficult
> > to introspect.
>
> You want texinfo-font-lock-keywords, I think.
>
>



  reply	other threads:[~2021-05-07  6:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 23:08 Lack of command highlighting in texinfo-mode Christopher Dimech
2021-05-06 23:12 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-07  6:10 ` Eli Zaretskii
2021-05-07  6:19   ` Christopher Dimech [this message]
2021-05-07  6:28     ` Eli Zaretskii
2021-05-07  6:50       ` 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-60ad2602-a289-4dc9-9d39-c7a64d22ab9d-1620368375980@3c-app-mailcom-bs12 \
    --to=dimech@gmx.com \
    --cc=eliz@gnu.org \
    --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).