From: Christopher Dimech <dimech@gmx.com>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Setting up user defined texinfo headlines using outline-heading-alist
Date: Fri, 14 May 2021 05:49:35 +0200 [thread overview]
Message-ID: <trinity-a990de32-d47f-4556-bb19-db12f0344ad2-1620964175250@3c-app-mailcom-bs03> (raw)
In-Reply-To: <CAP_d_8VCOw++5dA4ivi2dLfRpERc+HRR88MWnzLywG3nvtxXJA@mail.gmail.com>
I would be grateful for some explanation of variables "outline-regexp" and
"outline-heading-alist".
texinfo.el sets both "outline-heading-alist" and "outline-regexp", the latter from the
other using the same variable "texinfo-section-list".
Do we really need to have both outline-heading-alist and texinfo-section-list, because
as far as I can see we are using the same definition of headings and levels with the
variable "texinfo-section-list".
> Sent: Friday, May 14, 2021 at 7:13 AM
> From: "Yuri Khan" <yuri.v.khan@gmail.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: Re: Setting up user defined texinfo headlines using outline-heading-alist
>
> On Fri, 14 May 2021 at 01:35, Christopher Dimech <dimech@gmx.com> wrote:
>
> > It is then very easy to tell a user to learn more elisp, rather than convince a
> > developer to be consistent and write in ways that assist in the reuse of their
> > code.
>
> Yeah, much of the code in and around Emacs assumes the user can read,
> and often also write, Elisp.
>
> If you find outline-regexp in a docstring and you want to know where
> it’s defined and how it’s used, your best bet is to invoke
> xref-find-references on it and skim through the code.
>
> If you want to know how to have headings fontified, M-x find-library
> RET outline RET, then search for “face”, eventually find a variable
> ‘outline-font-lock-keywords’ and its use in ‘outline-mode’ but not in
> outline-minor-mode (probably because with outline-minor-mode you
> already have some fontification by the major mode). Maybe find a way
> to add ‘outline-font-lock-keywords’ to the major mode’s
> ‘font-lock-defaults’, but that definitely requires some programming.
>
>
next prev parent reply other threads:[~2021-05-14 3:49 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 14:21 outline-heading-alist for elisp using ";; * " Christopher Dimech
2021-05-10 21:08 ` Philip Kaludercic
2021-05-11 1:55 ` Christopher Dimech
2021-05-11 3:00 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-05-11 5:05 ` Christopher Dimech
2021-05-11 12:06 ` Jean Louis
2021-05-11 12:40 ` Christopher Dimech
2021-05-11 14:17 ` Jean Louis
2021-05-11 12:56 ` Christopher Dimech
2021-05-11 14:20 ` Jean Louis
2021-05-11 15:32 ` Christopher Dimech
2021-05-11 18:09 ` Jean Louis
2021-05-12 1:46 ` Christopher Dimech
2021-05-12 4:00 ` Jean Louis
2021-05-13 3:33 ` Christopher Dimech
2021-05-13 7:22 ` Jean Louis
2021-05-13 7:41 ` Christopher Dimech
2021-05-13 10:03 ` Jean Louis
2021-05-13 10:22 ` Christopher Dimech
2021-05-13 10:33 ` Jean Louis
2021-05-13 11:37 ` Christopher Dimech
2021-05-11 13:15 ` Christopher Dimech
2021-05-11 14:22 ` Jean Louis
2021-05-11 15:22 ` Christopher Dimech
2021-05-12 1:53 ` Christopher Dimech
2021-05-12 12:31 ` Stefan Monnier
2021-05-12 12:43 ` Christopher Dimech
2021-05-12 14:35 ` Yuri Khan
2021-05-12 14:52 ` Christopher Dimech
2021-05-13 12:29 ` Setting up user defined texinfo headlines using outline-heading-alist Christopher Dimech
2021-05-13 13:26 ` Yuri Khan
2021-05-13 15:10 ` Christopher Dimech
2021-05-13 16:05 ` Yuri Khan
2021-05-13 18:29 ` Jean Louis
2021-05-13 18:48 ` Christopher Dimech
2021-05-13 19:01 ` Yuri Khan
2021-05-13 18:35 ` Christopher Dimech
2021-05-13 19:13 ` Yuri Khan
2021-05-14 3:49 ` Christopher Dimech [this message]
2021-05-14 3:56 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-05-14 5:25 ` Christopher Dimech
2021-05-13 15:34 ` Jean Louis
2021-05-11 2:52 ` outline-heading-alist for elisp using ";; * " Christopher Dimech
2021-05-11 4:50 ` Jean Louis
2021-05-11 5:17 ` Christopher Dimech
2021-05-11 20:54 ` Jeremie Juste
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-a990de32-d47f-4556-bb19-db12f0344ad2-1620964175250@3c-app-mailcom-bs03 \
--to=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=yuri.v.khan@gmail.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.
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).