From: lisa-asket@perso.be
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: 49567@debbugs.gnu.org
Subject: bug#49567: outline level colours variability across major modes
Date: Thu, 15 Jul 2021 10:00:26 +0200 (CEST) [thread overview]
Message-ID: <ea-mime-60efeb1a-286e-296d26b1@www-7.mailo.com> (raw)
In-Reply-To: <87pmvkrpza.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
To: lisa-asket@perso.be
Subject: Re: bug#49567: outline level colours variability across major modes
Date: 15/07/2021 09:33:13 Europe/Paris
Cc: 49567@debbugs.gnu.org
lisa-asket@perso.be writes:
> Have seen that outline level colours change according to the major made. I do not like this, because
> I would like that outline colour levels be consistent across major modes.
Have you tried tweaking outline-minor-mode-highlight (introduced in
Emacs 28, i.e. on the master branch)? Setting it to 'override (and
reloading outline-minor-mode) does exactly what you would like, AFAICT
from reading the docstring, and trying it out.
Yes, I am forced to use 'override. It is weird because if I set my own outline highlight pattern
for a particular major-mode, I really want to override, otherwise I would use something else.
> Currently there is no facility for someone to define their own outline level colour schemes
> that in fixed across major modes.
Wouldn't customizing outline-[1-8] faces (plus setting
outline-minor-mode-highlight to 'override) allow exactly that?
How does that work? The code uses only colours from inherited faces. There is no way to set the
colour directly in hex.
[-- Attachment #2: Type: text/html, Size: 1500 bytes --]
next prev parent reply other threads:[~2021-07-15 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 5:31 bug#49567: outline level colours variability across major modes lisa-asket
2021-07-15 7:33 ` Kévin Le Gouguec
2021-07-15 8:00 ` lisa-asket [this message]
2021-07-16 4:44 ` lisa-asket
2021-07-16 9:09 ` Kévin Le Gouguec
2021-07-16 10:09 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ea-mime-60efeb1a-286e-296d26b1@www-7.mailo.com \
--to=lisa-asket@perso.be \
--cc=49567@debbugs.gnu.org \
--cc=kevin.legouguec@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.