unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#64227: Setting of outline levels for custom headings
@ 2023-06-22 16:18 uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2023-06-22 18:56 ` Juri Linkov
  0 siblings, 1 reply; 3+ messages in thread
From: uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2023-06-22 16:18 UTC (permalink / raw)
  To: 64227


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.


 







^ permalink raw reply	[flat|nested] 3+ messages in thread

* bug#64227: Setting of outline levels for custom headings
  2023-06-22 16:18 bug#64227: Setting of outline levels for custom headings uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
@ 2023-06-22 18:56 ` Juri Linkov
  2023-06-22 19:30   ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
  0 siblings, 1 reply; 3+ messages in thread
From: Juri Linkov @ 2023-06-22 18:56 UTC (permalink / raw)
  To: uzibalqa; +Cc: 64227

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?





^ permalink raw reply	[flat|nested] 3+ messages in thread

* bug#64227: Setting of outline levels for custom headings
  2023-06-22 18:56 ` Juri Linkov
@ 2023-06-22 19:30   ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
  0 siblings, 0 replies; 3+ messages in thread
From: uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2023-06-22 19:30 UTC (permalink / raw)
  To: Juri Linkov; +Cc: 64227


------- 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. 








^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-06-22 19:30 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-22 16:18 bug#64227: Setting of outline levels for custom headings uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-22 18:56 ` Juri Linkov
2023-06-22 19:30   ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors

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).