[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#64227: Setting of outline levels for custom headings
From: |
uzibalqa |
Subject: |
bug#64227: Setting of outline levels for custom headings |
Date: |
Thu, 22 Jun 2023 19:30:57 +0000 |
------- Original Message -------
On Friday, June 23rd, 2023 at 6:56 AM, Juri Linkov <juri@linkov.net> wrote:
> forcemerge 64177 64227
> stop
>
> > I am using outline-minor-mode and have changed outline-regexp,
> > outline-heading-alist.
> >
> > Have seen that for some major modes (e.g. emacs-lisp-mode), with
> > outline-minor-mode-highlight
> > set to 'override nil), one has to call (setq-local outline-level
> > 'outline-level) for the
> > heading faces to take effect.
> >
> > But without the call to outline-minor-mode-highlight, the headings defined
> > by outline-regexp
> > still get recognised, but not the outline levels.
> >
> > It is not evident at this point, which major modes require a call to
> > (setq-local outline-level 'outline-level).
> > There is not enough information in the documentation to get a custom
> > headings setup operational.
> >
> > Furthermore, although a call to (setq-local outline-level 'outline-level)
> > solved the problem,
> > a better approach would be for outline-minor-mode to automatically detect
> > whether a custom heading
> > was specified, and thus act accordingly. It would be quite a struggle for
> > people to perceive the
> > need to call (setq-local outline-level 'outline-level), as the change is
> > only needed for certain
> > major modes only.
>
>
> Why are you creating a new bug report instead of replying to the existing?
You provided a solution for my bug report with
(setq-local outline-level 'outline-level)
This is about a request to handle custom headings better, otherwise improving
documentation on how to set up custom headings and a simpler way to figure out
which major modes would require the additional outline-level call.