unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: pietru@caramail.com
Cc: help-gnu-emacs@gnu.org, monnier@iro.umontreal.ca
Subject: Re: headings for texinfo-mode using outline-minor-mode
Date: Wed, 12 May 2021 15:36:32 +0300	[thread overview]
Message-ID: <YJvL0K5oUixnSiG5@protected.localdomain> (raw)
In-Reply-To: <trinity-fd1654a6-9a01-438f-b756-6ad1d5cd364e-1620794625088@3c-app-mailcom-bs13>

* pietru@caramail.com <pietru@caramail.com> [2021-05-12 07:44]:
> > `texinfo-mode` is one of the rare modes which explicitly sets
> > `outline-heading-alist`, so you have the answer in there ;-)
> 
> Would it not be better for outline-minor-mode to set "outline-heading-alist"
> for each language.  Then, in each language mode, one simply calls the
> appropriate function.


That is the thought I assume each of us has.

There are many modes, various macros, functions. Many modes do not
have its outline structure. Emacs Lisp mode does not have "outline"
defined, we can just virtualize it and think how to create
outline. Its structure would greatly depend of the style, and comments
definition, for example to start writing (defun on the beginning of
the line. Each user can have different comment definition.

Modes which could be used with outline-minor-mode are especially those
with lightweight markup languages and some modes use
outline-minor-mode anyway, so for these it could be done:

adoc-mode and asciidoctor-mode
t2t-mode for txt2tags
markdown-mode 
latex-mode and similar TeX macros, like context-mode

I don't know for plain TeX-plain-tex-mode for example as \beginsection
is just one so far I know. TeX-plain-tex-mode is definitely usable for
reports that don't require elaborate structures. It is way easier to
create report with TeX-plain-tex-mode

Hello there

\beginsection
Here I am

\bye

Whoever now finds good outline-heading-alist post it here, please.


-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

Sign an open letter in support of Richard M. Stallman
https://stallmansupport.org/
https://rms-support-letter.github.io/




  parent reply	other threads:[~2021-05-12 12:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-11 16:43 headings for texinfo-mode using outline-minor-mode pietru
2021-05-11 17:26 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-05-12  4:43   ` pietru
2021-05-12 12:34     ` Stefan Monnier
2021-05-12 12:48       ` pietru
2021-05-12 14:04         ` Stefan Monnier
2021-05-12 14:15           ` pietru
2021-05-13  3:00       ` Christopher Dimech
2021-05-12 12:36     ` Jean Louis [this message]
2021-05-13  2:50       ` Christopher Dimech
2021-05-13  4:28         ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-05-13  4:46           ` Christopher Dimech
2021-05-13  9:06             ` Robert Thorpe
2021-05-13  9:39               ` Christopher Dimech
2021-05-13  7:20         ` Jean Louis
2021-05-13  7:36           ` Christopher Dimech
2021-05-13  3:57       ` Christopher Dimech
2021-05-12  5:11   ` pietru
2021-05-12  2:16 ` pietru
2021-05-12  2:39   ` pietru

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=YJvL0K5oUixnSiG5@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=pietru@caramail.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).