From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Cycling first N heading levels in outline Date: Mon, 24 May 2021 12:27:00 -0400 Message-ID: References: <87wnrqt5re.fsf@localhost> <875yz9bjrf.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18446"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Jean Louis , Ihor Radchenko , emacs-devel@gnu.org To: Christopher Dimech Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon May 24 18:28:22 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1llDRF-0004WZ-RQ for ged-emacs-devel@m.gmane-mx.org; Mon, 24 May 2021 18:28:21 +0200 Original-Received: from localhost ([::1]:36428 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1llDRD-0007A5-Lh for ged-emacs-devel@m.gmane-mx.org; Mon, 24 May 2021 12:28:19 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41924) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1llDQ8-0005O4-Rw for emacs-devel@gnu.org; Mon, 24 May 2021 12:27:12 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:47159) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1llDQ4-00087y-KL for emacs-devel@gnu.org; Mon, 24 May 2021 12:27:12 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 800B610028B; Mon, 24 May 2021 12:27:07 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 95FB71000C9; Mon, 24 May 2021 12:27:01 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1621873621; bh=nUSakTgzWgXqLsbjRrDV1Dost461gRa1zx/pPxKPNJo=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=H4hlcFEKdQU6MKZhC1RG6KY41AYBFS0W/bMBf7O3fsZ7ha7WafpISYxgQWMSkOOhG Ro7wsZ/JXzPY02IuUI5vHB/lj/ysa7OsewucJ62k5R9iv7sFdYHN4M25FY3C/tFm9c GsQybEfHiuGppOQo2vsbrcNj5j3y2R7yA95x5SzPkgCq8U6TUrKbsGhV1Kdkob8fAp 7RC4S8KbrTYQy7BMyXE8GGEy3WfvtBVC3q48oZtl/BHoEiyaI42bPYnHVQPRsM+eSa bdtYWL+lfUq+Lup34bX50kmngfFjkgGlEvg/gkWtf8JYXFcAOY52yyWa6GE83SXJ3N TEE+i7+u08ObQ== Original-Received: from alfajor (69-196-163-239.dsl.teksavvy.com [69.196.163.239]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 43E2F120254; Mon, 24 May 2021 12:27:01 -0400 (EDT) In-Reply-To: (Christopher Dimech's message of "Mon, 24 May 2021 12:39:15 +0200") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:269773 Archived-At: > 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. Stefan