From: Juri Linkov <juri@linkov.net>
To: pauline-galea@gmx.com
Cc: 48710@debbugs.gnu.org
Subject: bug#48710: Retaining code highlighting (for defun, defvar) in outline mode
Date: Sun, 30 May 2021 00:55:10 +0300 [thread overview]
Message-ID: <87zgwd42sd.fsf@mail.linkov.net> (raw)
In-Reply-To: <trinity-19fb89f7-eb64-462f-a98e-a6682174cdda-1622164650847@3c-app-mailcom-bs04> (pauline-galea@gmx.com's message of "Fri, 28 May 2021 03:17:30 +0200")
tags 48710 notabug
close 48710 28.0.50
thanks
> Currently outline mode changes the colour of headings and subheadings.
>
> But I have noticed that elisp structures are also considered as headings.
> This results in some code highlighting problems for things like "defun"
> and "defvar" because the whole line gets a one colour highlighting in
> a way that is similar to a heading face.
>
> It would be better that elisp code structures retain the original code highlighting,
> but keep the ... at the end of the line to show that the code body is hidden.
> The ... could be highligted instead instead.
>
> For more flexibility, it would be beneficial to have a separate keybinding that toggles
> between showing the contents (body) of a code structure and hiding it, that is independent
> of headings.
It seems this is already implemented: when you customize
outline-minor-mode-highlight to a value 't' or 'append' (but not 'override'),
and also customize outline-minor-mode-cycle to t, then after
enabling outline-minor-mode, and typing S-TAB S-TAB on a heading
it keeps the ... at the end of lines, while
retaining the original code highlighting.
Please reopen this report, when you still see a problem
and can't get it working.
prev parent reply other threads:[~2021-05-29 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 1:17 bug#48710: Retaining code highlighting (for defun, defvar) in outline mode pauline-galea
2021-05-29 21:55 ` Juri Linkov [this message]
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=87zgwd42sd.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=48710@debbugs.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.
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).