From: Heime <heimeborgia@protonmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Adding colour when font-lock in disabled
Date: Fri, 09 Dec 2022 08:26:52 +0000 [thread overview]
Message-ID: <bMiSDzLAFo_mGDLlimfiLF4azDP8PDFE_1Edvi4o9z8_N66IUvHy3XLHRwYipeHoH6e5QHiN8nLyCAeheuH18ijnr5mREYdjDNsU-0BrKz8=@protonmail.com> (raw)
In-Reply-To: <838rjh12ar.fsf@gnu.org>
------- Original Message -------
On Friday, December 9th, 2022 at 7:09 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Fri, 09 Dec 2022 01:46:18 +0000
> > From: Heime heimeborgia@protonmail.com
> > Cc: Heime via Users list for the GNU Emacs text editor help-gnu-emacs@gnu.org
> >
> > > From what I understand, when font-lock-mode is enabled, it takes over the face property but provides an alias property - font-lock-face. The font-lock-face property bypasses font-lock to allow coloured text.
> >
> > Really weird stuff because if you want to allow someone to specify face property, just allow them to specify it.
>
>
> What is weird about it? font-lock-mode places face properties
> according to the mode's definitions, so it will overwrite any face
> properties you put manually. Thus the need to use a different
> property, which font-lock-mode doesn't control.
If I want to use and enforce colour property, could there be a function that sets the colour irrpespective of whether font-lock is "on" or "off" ?
Perhaps I should avoid using fundamental-mode as a useful mode to work with. Is it a rule that when a new buffer is made, it goes into fundamental-mode where font-lock is off ?
next prev parent reply other threads:[~2022-12-09 8:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 0:50 Adding colour when font-lock in disabled Heime
2022-12-09 1:46 ` Heime
2022-12-09 7:09 ` Eli Zaretskii
2022-12-09 8:09 ` Heime
2022-12-09 12:06 ` Eli Zaretskii
2022-12-09 12:27 ` Heime
2022-12-09 12:36 ` Eli Zaretskii
2022-12-09 13:04 ` Heime
2022-12-09 14:53 ` Eli Zaretskii
2022-12-09 18:54 ` Jean Louis
2022-12-09 21:39 ` [External] : " Drew Adams
2022-12-09 23:19 ` Heime
2022-12-10 7:31 ` Eli Zaretskii
2022-12-10 8:31 ` Heime
2022-12-10 8:50 ` Eli Zaretskii
2022-12-10 11:06 ` Heime
2022-12-09 8:26 ` Heime [this message]
2022-12-09 12:07 ` Eli Zaretskii
2022-12-09 13:48 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-12-10 1:59 ` Emanuel Berg
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='bMiSDzLAFo_mGDLlimfiLF4azDP8PDFE_1Edvi4o9z8_N66IUvHy3XLHRwYipeHoH6e5QHiN8nLyCAeheuH18ijnr5mREYdjDNsU-0BrKz8=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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).