From: Howard Melman <hmelman@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 46878@debbugs.gnu.org
Subject: bug#46878: 27.1; lisp-outline-level returns imprecise level number
Date: Wed, 3 Mar 2021 15:04:25 -0500 [thread overview]
Message-ID: <44DA0D54-D744-41A3-A7A1-D6A45B9536A4@gmail.com> (raw)
In-Reply-To: <87mtvkcfr1.fsf@mail.linkov.net>
> On Mar 3, 2021, at 2:04 PM, Juri Linkov <juri@linkov.net> wrote:
>
> Some packages like https://jurta.org/en/emacs/ee/outline
> showed all 4 useless additional levels.
>
> Now thanks to your new definition, all such visual noise is removed:
>
> - (no-heading)
> - (no-heading)
> - (no-heading)
> - (no-heading)
>
> and only one top heading is displayed:
>
> - (no-heading)
> ;;; ee-outline.el --- manipulate outlines collected from outline-mode
> ;;; Commentary:
> - ;;; Code:
Great. I came about it because I hope consult-outline adds an argument
to let the user choose headings from the top N levels, so that's why the
numbering became important for me.
Hopefully no reports a downside which is why I asked about any visible
changes in what is shipped with emacs.
Howard
next prev parent reply other threads:[~2021-03-03 20:04 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
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 [this message]
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=44DA0D54-D744-41A3-A7A1-D6A45B9536A4@gmail.com \
--to=hmelman@gmail.com \
--cc=46878@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).