unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Jean Louis <bugs@gnu.support>
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 09:36:20 +0200	[thread overview]
Message-ID: <trinity-2b11172f-c6ac-4b93-a65c-deee3c7c4813-1620891380464@3c-app-mailcom-bs15> (raw)
In-Reply-To: <YJzTRLXHC61117Dg@protected.localdomain>


> Sent: Thursday, May 13, 2021 at 7:20 PM
> From: "Jean Louis" <bugs@gnu.support>
> 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
>
> * Christopher Dimech <dimech@gmx.com> [2021-05-13 05:50]:
> > > 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.
> >
> > 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.
>
> Hmm...
>
> Maybe strategy is not best hypothetically, but practically it is
> useful to collapse code structures: I can get the easy overview or
> quick index of functions and faster do the movements. Also copy and
> paste is easier.

I absolutely agree that collapse code structures and code structure movements
improves coding practice.  Then with headings you can categorise various sections
of the file that could also be independently manipulated.

At this point, it would first be beneficial to handle the specification of
outline-heading-alist that users could successfully adapt te their needs.

Currently I want to handle texinfo files first because there is already
outline-heading-alist being defined in "texinfo.el".  Then look at elisp.

> Only "(" in the first column is collaped.
>
> --
> 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/
>
>
>



  reply	other threads:[~2021-05-13  7: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
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 [this message]
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-2b11172f-c6ac-4b93-a65c-deee3c7c4813-1620891380464@3c-app-mailcom-bs15 \
    --to=dimech@gmx.com \
    --cc=bugs@gnu.support \
    --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).