From: Christopher Dimech <dimech@gmx.com>
To: monnier@iro.umontreal.ca
Cc: help-gnu-emacs@gnu.org
Subject: Re: headings for texinfo-mode using outline-minor-mode
Date: Thu, 13 May 2021 06:46:48 +0200 [thread overview]
Message-ID: <trinity-9d2e439f-4e15-4edf-9158-965cfeef9c10-1620881208711@3c-app-mailcom-bs15> (raw)
In-Reply-To: <jwvh7j7cl6z.fsf-monnier+emacs@gnu.org>
> Sent: Thursday, May 13, 2021 at 4:28 PM
> From: "Stefan Monnier via Users list for the GNU Emacs text editor" <help-gnu-emacs@gnu.org>
> To: help-gnu-emacs@gnu.org
> Subject: Re: headings for texinfo-mode using outline-minor-mode
>
> > Being able to have different comment definition for headings would be very valuable.
> > I also like the idea that headings become different than code. This is because, you
> > could collapse code independently of headers. Currently code structures are being
> > used as headers, a strategy which is faulty from my point of view.
>
> Then you don't want `outline-minor-mode`. You might like `allout-mode`.
I am saying to clean up outline-minor-mode and write clear instructions on how
to set up user defined outline-heading-alist. This is because outline-minor-mode
has much greater use for code.
> Stefan
>
>
>
next prev parent reply other threads:[~2021-05-13 4:46 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
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 [this message]
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=trinity-9d2e439f-4e15-4edf-9158-965cfeef9c10-1620881208711@3c-app-mailcom-bs15 \
--to=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).