GNU bug report logs - #64227
Setting of outline levels for custom headings

Previous Next

Package: emacs;

Reported by: uzibalqa <uzibalqa <at> proton.me>

Date: Thu, 22 Jun 2023 16:20:01 UTC

Severity: normal

Merged with 64177

Done: Juri Linkov <juri <at> linkov.net>

Bug is archived. No further changes may be made.

Full log


Message #8 received at 64227 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> linkov.net>
To: uzibalqa <uzibalqa <at> proton.me>
Cc: 64227 <at> debbugs.gnu.org
Subject: Re: bug#64227: Setting of outline levels for custom headings
Date: Thu, 22 Jun 2023 21:56:41 +0300
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?




This bug report was last modified 1 year and 334 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.