From: Christopher Dimech <dimech@gmx.com>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
Jean Louis <bugs@gnu.support>,
Ihor Radchenko <yantar92@gmail.com>
Subject: Cycling first N heading levels in outline
Date: Mon, 24 May 2021 13:23:33 +0200 [thread overview]
Message-ID: <trinity-9ecb548a-0598-4911-9d1f-f8089b463d0f-1621855413182@3c-app-mailcom-bs01> (raw)
In-Reply-To: <87im381js1.fsf@gmail.com>
I am using GNU Emacs 27.1 and that functionality is not present. Have tried to install
the development version and am getting
checking for libXaw... configure: error: No X toolkit could be found.
> Sent: Monday, May 24, 2021 at 10:57 PM
> From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Stefan Monnier" <monnier@iro.umontreal.ca>, "Ihor Radchenko" <yantar92@gmail.com>, "Jean Louis" <bugs@gnu.support>, emacs-devel@gnu.org
> Subject: Re: Cycling first N heading levels in outline
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> >> The convention used in ELisp is:
> >>
> >> ;;; Section
> >> ;;;; Subsection
> >> ;;;;; Subsubsection
> >> ;;;;;; Subsubsubsection
> >> ;;;;;;; Subsubsubsubsection
> >> [...]
> >
> > The headings still look like comments, whereas they are supposed to get highlighted
> > according to the heading level.
> >
> > Could we get that to work in said way?
>
> On Emacs master, the outline-minor-mode-highlight option allows you to
> customize how headings are fontified:
>
> > When t, it puts outline faces only if there are no major mode’s faces
> > on headings. When ‘override’, it completely overwrites major mode’s
> > faces with outline faces. When ‘append’, it tries to append outline
> > faces to major mode’s faces.
>
next prev parent reply other threads:[~2021-05-24 11:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 16:16 Cycling first N heading levels in outline Christopher Dimech
2021-05-23 4:48 ` Ihor Radchenko
2021-05-23 8:58 ` Christopher Dimech
2021-05-23 9:46 ` Ihor Radchenko
2021-05-23 9:53 ` Christopher Dimech
2021-05-23 10:21 ` Ihor Radchenko
2021-05-23 10:23 ` Ihor Radchenko
2021-05-23 13:10 ` Christopher Dimech
2021-05-23 14:14 ` Ihor Radchenko
2021-05-23 14:14 ` Jean Louis
2021-05-23 14:34 ` Christopher Dimech
2021-05-23 14:37 ` Jean Louis
2021-05-23 14:12 ` Jean Louis
2021-05-23 14:35 ` Ihor Radchenko
2021-05-23 17:57 ` Jean Louis
2021-05-23 18:55 ` Christopher Dimech
2021-05-23 19:06 ` Tassilo Horn
2021-05-23 19:55 ` Stefan Monnier
2021-05-24 10:34 ` Christopher Dimech
2021-05-24 10:57 ` Kévin Le Gouguec
2021-05-24 11:23 ` Christopher Dimech [this message]
2021-05-25 17:41 ` Christopher Dimech
2021-05-24 10:39 ` Christopher Dimech
2021-05-24 16:27 ` Stefan Monnier
2021-05-24 17:43 ` Christopher Dimech
2021-05-26 13:57 ` Ihor Radchenko
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=trinity-9ecb548a-0598-4911-9d1f-f8089b463d0f-1621855413182@3c-app-mailcom-bs01 \
--to=dimech@gmx.com \
--cc=bugs@gnu.support \
--cc=emacs-devel@gnu.org \
--cc=kevin.legouguec@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=yantar92@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 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).