From: Christopher Dimech <dimech@gmx.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Ihor Radchenko <yantar92@gmail.com>,
Jean Louis <bugs@gnu.support>,
emacs-devel@gnu.org
Subject: Cycling first N heading levels in outline
Date: Mon, 24 May 2021 19:43:06 +0200 [thread overview]
Message-ID: <trinity-8dde06a5-704e-4c9c-8cbe-ee83be3aedcb-1621878186610@3c-app-mailcom-bs01> (raw)
In-Reply-To: <jwvlf84xfqa.fsf-monnier+emacs@gnu.org>
> Sent: Tuesday, May 25, 2021 at 4:27 AM
> From: "Stefan Monnier" <monnier@iro.umontreal.ca>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Jean Louis" <bugs@gnu.support>, "Ihor Radchenko" <yantar92@gmail.com>, emacs-devel@gnu.org
> Subject: Re: Cycling first N heading levels in outline
>
> > I have looked at how functions are folded. But if you call elisp code (which
> > always involves using parentheses) they also get to be interpreted as headings.
> > Can this be fixed please, so that only elisp structure constructs are interpreted
> > as headlines [e.g. "(defun" "(defvar"].
>
> This is not a bug but a feature. If you want to group several ELisp
> code entries together, you can wrap them in a `progn` (or something
> else like Setup's `setup` macro, or `use-package`, ...).
>
> In ELisp packages (as opposed to user config files), there pretty much
> shouldn't be any function calls at top-level, since loading such a file
> should have virtually no user-visible effect.
It is more of an assumption then. User Config Files should then not be too
extensive, or otherwise organised into a number ofspecific functions.
What can one use to unfold and fold a specific function?
next prev parent reply other threads:[~2021-05-24 17:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 16:16 Cycling first N heading levels in outline Christopher Dimech
2021-05-23 4:48 ` Ihor Radchenko
2021-05-23 8:58 ` Christopher Dimech
2021-05-23 9:46 ` Ihor Radchenko
2021-05-23 9:53 ` Christopher Dimech
2021-05-23 10:21 ` Ihor Radchenko
2021-05-23 10:23 ` Ihor Radchenko
2021-05-23 13:10 ` Christopher Dimech
2021-05-23 14:14 ` Ihor Radchenko
2021-05-23 14:14 ` Jean Louis
2021-05-23 14:34 ` Christopher Dimech
2021-05-23 14:37 ` Jean Louis
2021-05-23 14:12 ` Jean Louis
2021-05-23 14:35 ` Ihor Radchenko
2021-05-23 17:57 ` Jean Louis
2021-05-23 18:55 ` Christopher Dimech
2021-05-23 19:06 ` Tassilo Horn
2021-05-23 19:55 ` Stefan Monnier
2021-05-24 10:34 ` Christopher Dimech
2021-05-24 10:57 ` Kévin Le Gouguec
2021-05-24 11:23 ` Christopher Dimech
2021-05-25 17:41 ` Christopher Dimech
2021-05-24 10:39 ` Christopher Dimech
2021-05-24 16:27 ` Stefan Monnier
2021-05-24 17:43 ` Christopher Dimech [this message]
2021-05-26 13:57 ` Ihor Radchenko
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-8dde06a5-704e-4c9c-8cbe-ee83be3aedcb-1621878186610@3c-app-mailcom-bs01 \
--to=dimech@gmx.com \
--cc=bugs@gnu.support \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=yantar92@gmail.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).