unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 64227@debbugs.gnu.org
Subject: bug#64227: Setting of outline levels for custom headings
Date: Thu, 22 Jun 2023 16:18:59 +0000	[thread overview]
Message-ID: <W6kdw13gG0xGVyNpIYpsNqHlGJrRWajjawFmcJT_8EkKfe1oBJk04rsO0oRmUFlp8VPplrm6wRZqFlXZVEv-Te-juKAwKhufDIitm7ZSrPQ=@proton.me> (raw)


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.


 







             reply	other threads:[~2023-06-22 16:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-22 16:18 uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-06-22 18:56 ` bug#64227: Setting of outline levels for custom headings Juri Linkov
2023-06-22 19:30   ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors

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='W6kdw13gG0xGVyNpIYpsNqHlGJrRWajjawFmcJT_8EkKfe1oBJk04rsO0oRmUFlp8VPplrm6wRZqFlXZVEv-Te-juKAwKhufDIitm7ZSrPQ=@proton.me' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=64227@debbugs.gnu.org \
    --cc=uzibalqa@proton.me \
    /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).