From: Juri Linkov <juri@linkov.net>
To: Howard Melman <hmelman@gmail.com>
Cc: 46878@debbugs.gnu.org
Subject: bug#46878: 27.1; lisp-outline-level returns imprecise level number
Date: Wed, 03 Mar 2021 21:04:18 +0200 [thread overview]
Message-ID: <87mtvkcfr1.fsf@mail.linkov.net> (raw)
In-Reply-To: <54FD8677-43E1-4806-9F8D-86850CBC3B29@gmail.com> (Howard Melman's message of "Tue, 2 Mar 2021 19:25:56 -0500")
>> I use outline-minor-mode extensively in lisp-mode,
>> so after trying your version I'd say that while
>> the change of the level definition can be surprising
>> to someone, but to me your version makes more sense than
>> the current level definition.
>
> Thanks. I use outline-minor-mode a bit, mostly via outline-cycle.
bug#45147 implemented new modes for Org-like TAB cycling in outline-minor-mode.
> When you say the change can be surprising, what do you mean? Does something
> show the level number? AFAIK levels are just treated in relation to each
> other and the number isn't shown to the user. My change I think just means
> levels 1-4 were previously unused and are now used.
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:
next prev parent reply other threads:[~2021-03-03 19: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 [this message]
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=87mtvkcfr1.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=46878@debbugs.gnu.org \
--cc=hmelman@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).