From: Philip Kaludercic <philipk@posteo.net>
To: pauline-galea@gmx.com
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: "emacs-28.0.50 -q" and "emacs-28.0.50 -Q" with outline-minor-mode-highlight
Date: Thu, 27 May 2021 17:34:22 +0000 [thread overview]
Message-ID: <877djkozc1.fsf@icterid> (raw)
In-Reply-To: <trinity-5332e9f2-3f50-4479-a243-71c99938f701-1622135005475@3c-app-mailcom-bs04> (pauline-galea@gmx.com's message of "Thu, 27 May 2021 19:03:25 +0200")
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
pauline-galea@gmx.com writes:
>> Sent: Friday, May 28, 2021 at 1:47 AM
>> From: "Philip Kaludercic" <philipk@posteo.net>
>> To: pauline-galea@gmx.com
>> Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
>> Subject: Re: "emacs-28.0.50 -q" and "emacs-28.0.50 -Q" with
>> outline-minor-mode-highlight
>>
>> pauline-galea@gmx.com writes:
>>
>> >> I am guessing that you should first set outline-minor-mode-highlight
>> >> then activate outline-minor-mode. Setting a variable directly usually
>> >> does not perform any changes. - Philip
>> >
>> > No, that does not work.
>>
>> I just tried it using my local master checkout I just built this
>> morning, and it worked... Are you sure your major mode initializes
>> outline-minor-mode properly?
>
> Do you get different heading colours for the three heading levels below?
>
> ;;; * heading 1
> ;; brief body
> ;;;; ** subheading 1.1
> ;; brief body
> ;;;;; *** subsubheading 1.1.1
> ;; brief body
Yes, I'll attach a screenshot below. It's not pretty, but I notice a
difference.
--
Philip K.
[-- Attachment #2: Screenshot_2021-05-27_19-33-38.png --]
[-- Type: image/png, Size: 49737 bytes --]
next prev parent reply other threads:[~2021-05-27 17:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 17:35 "emacs-28.0.50 -q" and "emacs-28.0.50 -Q" with outline-minor-mode-highlight pauline-galea
2021-05-27 9:54 ` Philip Kaludercic
2021-05-27 13:38 ` pauline-galea
2021-05-27 13:47 ` Philip Kaludercic
2021-05-27 15:07 ` pauline-galea
2021-05-27 17:06 ` Philip Kaludercic
2021-05-27 17:13 ` pauline-galea
2021-05-27 17:03 ` pauline-galea
2021-05-27 17:34 ` Philip Kaludercic [this message]
2021-05-27 18:13 ` pauline-galea
2021-05-27 18:27 ` Stephen Berman
2021-05-27 18:36 ` pauline-galea
2021-05-27 18:58 ` Stephen Berman
2021-05-27 19:11 ` pauline-galea
2021-05-27 19:04 ` Philip Kaludercic
2021-05-27 19:17 ` pauline-galea
2021-05-27 19:22 ` Philip Kaludercic
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=877djkozc1.fsf@icterid \
--to=philipk@posteo.net \
--cc=help-gnu-emacs@gnu.org \
--cc=pauline-galea@gmx.com \
/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.
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).