unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: pauline-galea@gmx.com
Cc: 48610@debbugs.gnu.org
Subject: bug#48610: texinfo heading levels not highlighted by outline-minor-mode
Date: Fri, 28 May 2021 01:33:54 +0300	[thread overview]
Message-ID: <87bl8vrfj1.fsf@mail.linkov.net> (raw)
In-Reply-To: <trinity-b4977a90-6c17-4d80-a6f4-6c5991381cda-1621977374217@3c-app-mailcom-bs01> (pauline-galea@gmx.com's message of "Tue, 25 May 2021 23:16:14 +0200")

> This is what I am using
>
> (defvar hdlevels
>    '( ("@chapter" . 1)
>       ("@section" . 1)
>       ("@subsection" . 2)
>       ("@subsubsection" . 3)
>       ;; ---------------------------------------------------------
>       ("@unnumbered" . 1)
>       ("@unnumberedsec" . 1)
>       ("@unnumberedsubsec" . 2)
>       ("@unnumberedsubsubsec" . 3)
>       ;; ---------------------------------------------------------
>       ("@appendix" . 1)
>       ("@appendixsec" . 1)
>       ("@appendixsubsec" . 2)
>       ("@appendixsubsubsec" . 3)
>       ;; ---------------------------------------------------------
>       ("@majorheading" . 1)
>       ("@chapheading" . 1)
>       ("@heading" . 1)
>       ("@subheading" . 2)
>       ("@subsubheading" . 3) )
>    "Sets heading names and levels for texinfo files." )

I tried your definitions, and then outlines are highlighted.

I wonder why outline-regexp defined in texinfo-mode is broken?
What would be a correct regexp for texinfo-mode?





  reply	other threads:[~2021-05-27 22:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-23  9:44 bug#48610: texinfo heading levels not highlighted by outline-minor-mode pauline-galea
2021-05-25 20:23 ` Juri Linkov
2021-05-25 20:50   ` pauline-galea
2021-05-25 21:16   ` pauline-galea
2021-05-27 22:33     ` Juri Linkov [this message]
2021-05-29 21:43 ` Juri Linkov

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=87bl8vrfj1.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=48610@debbugs.gnu.org \
    --cc=pauline-galea@gmx.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).