From: Howard Melman <hmelman@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 46878@debbugs.gnu.org
Subject: bug#46878: 27.1; lisp-outline-level returns imprecise level number
Date: Tue, 2 Mar 2021 12:48:37 -0500 [thread overview]
Message-ID: <36425FB3-9EAE-4050-A6B0-AA4AAE57C10A@gmail.com> (raw)
In-Reply-To: <83sg5d5vw5.fsf@gnu.org>
On Mar 2, 2021, at 12:05 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: Howard Melman <hmelman@gmail.com>
>> Date: Tue, 2 Mar 2021 11:35:01 -0500
>>
>> lisp-outline-level returns a functional but incorrect level
>> number. Comments beginning with ";;; " should be at level 1
>> but it returns 5 because they match ";;; [^ \t\n]" and the
>> current code just returns that length.
>
> I believe these problems are fixed on the master branch (or at least
> the behavior is very different), please try that.
I don't build my own emacs and can't easily test on master.
I had previously confirmed that lisp-outline-level in 27.1
is the same as in master as shown here:
http://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/emacs-lisp/lisp-mode.el
You can quickly test the behavior by putting point at the beginning
of a "heading" line in an emacs-lisp-mode file and running:
(progn (looking-at outline-regexp) (funcall outline-level))
Howard
next prev parent reply other threads:[~2021-03-02 17:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 16:35 bug#46878: 27.1; lisp-outline-level returns imprecise level number Howard Melman
2021-03-02 17:05 ` Eli Zaretskii
2021-03-02 17:48 ` Howard Melman [this message]
2021-03-02 19:36 ` Juri Linkov
2021-03-03 0:25 ` Howard Melman
2021-03-03 19:04 ` Juri Linkov
2021-03-03 20:04 ` Howard Melman
2021-03-07 18:45 ` Juri Linkov
2021-03-07 18:57 ` Howard Melman
2021-03-08 17:23 ` Juri Linkov
2021-03-08 17:38 ` Howard Melman
2021-03-08 17:52 ` Juri Linkov
2021-03-21 2:23 ` Gabriel
2021-03-21 20:17 ` Juri Linkov
2021-03-24 1:34 ` Howard Melman
2021-05-18 1:12 ` Howard Melman
2021-05-18 20:36 ` Juri Linkov
2021-05-18 23:38 ` Howard Melman
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=36425FB3-9EAE-4050-A6B0-AA4AAE57C10A@gmail.com \
--to=hmelman@gmail.com \
--cc=46878@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).