unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: Christopher Dimech <dimech@gmx.com>
Cc: help-gnu-emacs@gnu.org, monnier@iro.umontreal.ca
Subject: Re: headings for texinfo-mode using outline-minor-mode
Date: Thu, 13 May 2021 10:06:44 +0100	[thread overview]
Message-ID: <87bl9fc89n.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <trinity-9d2e439f-4e15-4edf-9158-965cfeef9c10-1620881208711@3c-app-mailcom-bs15> (message from Christopher Dimech on Thu, 13 May 2021 06:46:48 +0200)

Christopher Dimech <dimech@gmx.com> writes:

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

I disagree.

Outline-mode and outline-minor-mode are simple.  They're made to do
simple and predictable things.  That's the point of them.

We have Org-mode because people want something more than what
outline-mode provides by itself.  We also have things like outshine-mode
and allout-mode because people want more than what outline-mode does by
itself.  But not everybody wants more that's why outline-mode and
outline-minor-mode still exist!

It seems that you are trying to make outline-mode into outshine-mode.
There's no need to do that, we already have outshine-mode.

If you're not doing that, then I don't understand what you are doing.
That's not surprising since so many of your emails are so vague.  You
have to learn to express yourself more clearly as Yuri Khan said.

Also, to write a new mode you have to learn elisp in more depth.  This
project you're doing is a vehicle for doing that certainly.  But
remember that the existing modes I've mentioned were probably written by
people who already knew elisp.

BR,
Robert Thorpe



  reply	other threads:[~2021-05-13  9:06 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
2021-05-13  9:06             ` Robert Thorpe [this message]
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=87bl9fc89n.fsf@robertthorpeconsulting.com \
    --to=rt@robertthorpeconsulting.com \
    --cc=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).