From: Juri Linkov <juri@linkov.net>
To: Christopher Dimech <dimech@gmx.com>
Cc: 48724@debbugs.gnu.org
Subject: bug#48724: Code collapsing and outline headings for elisp
Date: Tue, 01 Jun 2021 23:44:07 +0300 [thread overview]
Message-ID: <87sg21cqe8.fsf@mail.linkov.net> (raw)
In-Reply-To: <trinity-e5a3f933-0d03-4e46-968d-54931397c9ad-1622546682659@3c-app-mailcom-bs01> (Christopher Dimech's message of "Tue, 1 Jun 2021 13:24:42 +0200")
> I suggest that emacs-lisp-mode does code collapse (show/hide) by default.
> Then outline-minor-mode does additional headings in the form
>
> ;;; Heading 1
> ;;;; SubHeading
> ;;;;; SubSubHeading
>
> ;;; Heading 2
>
> outline-minor-mode would then be made to collapse sections of code between
> headlines.
>
> This means that a headline hide could hide a number of variable and function
> definitions that belong together.
Recently we changed the outlines of emacs-lisp-mode in https://debbugs.gnu.org/46878
So this is already fixed.
next prev parent reply other threads:[~2021-06-01 20:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <trinity-a2e798f1-1257-407e-8dfc-4ad92004a227-1622516668807@3c-app-mailcom-bs01>
[not found] ` <877djegtaq.fsf@protesilaos.com>
[not found] ` <trinity-53de0a34-f881-4ec9-b2e8-901b97d0d76f-1622519072162@3c-app-mailcom-bs01>
[not found] ` <8735u2grnc.fsf@protesilaos.com>
[not found] ` <trinity-fd06ae24-9c88-47ec-8fd1-e93789f670bf-1622551360761@3c-app-mailcom-bs01>
[not found] ` <87bl8pwvdb.fsf@protesilaos.com>
2021-05-28 20:59 ` bug#48724: Code collapsing and outline headings for elisp Christopher Dimech
2021-05-29 21:57 ` Juri Linkov
2021-05-29 23:55 ` Christopher Dimech
2021-05-30 1:38 ` Christopher Dimech
2021-05-30 22:15 ` Juri Linkov
2021-05-30 23:58 ` Christopher Dimech
2021-06-01 11:24 ` Christopher Dimech
2021-06-01 20:44 ` Juri Linkov [this message]
2021-06-02 0:07 ` Christopher Dimech
2021-06-02 20:54 ` Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sg21cqe8.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=48724@debbugs.gnu.org \
--cc=dimech@gmx.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.