unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 45147@debbugs.gnu.org
Subject: bug#45147: Org-like cycling in outline-minor-mode
Date: Sun, 16 May 2021 20:53:49 +0300	[thread overview]
Message-ID: <87im3i7efm.fsf@mail.linkov.net> (raw)
In-Reply-To: <87zgwullsb.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 16 May 2021 17:51:16 +0200")

>>> As suggested in bug#41198, here is a patch that adds
>>> two new options (disabled by default):
>>
>> With no objections, new options (disabled by default)
>> pushed to master.
>
> Skimming this thread, I'm not quite sure whether there's anything more
> to be done here?  The first message mentioned

There is still an unpushed patch outline-describe-bindings.patch in
https://debbugs.gnu.org/45147#18 that will enable outline-minor-mode
on the output of describe-bindings.  I waited when the speed of
describe-bindings will be improved in bug#45379, but maybe
this patch could be pushed nevertheless.

>> - outline-minor-mode-font-lock that enables outline font-lock in
>>   outline-minor-mode
>
> which does not seem to exist, but I'm not sure whether the second
> version made that unnecessary...

outline-minor-mode-font-lock was renamed to
outline-minor-mode-highlight.





  reply	other threads:[~2021-05-16 17:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09 19:15 bug#45147: Org-like cycling in outline-minor-mode Juri Linkov
2020-12-09 20:03 ` Juri Linkov
2020-12-14 20:35   ` Juri Linkov
2020-12-16 20:28     ` Juri Linkov
2021-03-03 19:12 ` Juri Linkov
2021-05-16 15:51   ` Lars Ingebrigtsen
2021-05-16 17:53     ` Juri Linkov [this message]
2021-05-17 13:57       ` Lars Ingebrigtsen
2021-05-18 20:12         ` Juri Linkov
2021-05-19 12:10           ` Eli Zaretskii
2021-05-19 16:14             ` Juri Linkov
2021-05-19 17:28               ` Eli Zaretskii
2021-05-20 18:37                 ` Juri Linkov

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=87im3i7efm.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=45147@debbugs.gnu.org \
    --cc=larsi@gnus.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).