From: Heime via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Heime <heimeborgia@protonmail.com>
Cc: Yuan Fu <casouri@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
59828-done@debbugs.gnu.org
Subject: bug#59828: Fundamental Mode buffers fail to keep text properties
Date: Thu, 08 Dec 2022 13:00:11 +0000 [thread overview]
Message-ID: <VTid1_Y0Kc_pxoIErZhbUlB0fNG4mMO0tEQ3PgJz0u7SV-SjK1_ISSl9KhgYuO3AAUAUH04uomxEn6gm_Unl42NRDcu253iQFL2WJc1r0AA=@protonmail.com> (raw)
In-Reply-To: <dKDOTbu7B5yYiCdsSGhTdvO301BfxEgywJodFdMz6h3do5mbvdcPDbFGDs8KaE4VMQs61Ve3AzbFLfWEd2-IpcC9QYI09az7xbbhtv5xnUs=@protonmail.com>
------- Original Message -------
On Wednesday, December 7th, 2022 at 12:53 AM, Heime via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org> wrote:
> ------- Original Message -------
> On Tuesday, December 6th, 2022 at 5:41 AM, Yuan Fu casouri@gmail.com wrote:
>
>
>
> > > > > Just to clarify:
> > > > >
> > > > > 1. If font-lock-mode is off, you should use (propertize … ‘face …)
> > > > > 2. If font-lock-mode is on, you should use (propertize … ‘font-lock-face …)
> > >
> > > If I have a function that does the inserts, should I include the two different conditions,
> > > whether "font-lock-mode" in "off" or "on" ?
> > >
> > > Test whether font-lock-mode is off, then use (propertize … ‘face …)
> > > Test whether font-lock-mode is on, then use (propertize … ‘font-lock-face …)
> >
> > It depends on your use-case. If you want to be safe you can just apply both properties, then it will work no matter font-lock-mode is on or not.
> >
> > Yuan
I thought the procedure is to enable "font-lock-mode", followed by
(propertize "G" 'font-lock-face '(:foreground "black")). Finally disabling "font-lock-mode" in that buffer.
prev parent reply other threads:[~2022-12-08 13:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 6:30 bug#59828: Fundamental Mode buffers fail to keep text properties Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-05 6:32 ` Yuan Fu
2022-12-05 8:30 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-05 12:46 ` Eli Zaretskii
2022-12-05 13:49 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-05 14:41 ` Eli Zaretskii
2022-12-05 14:54 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-05 15:00 ` Eli Zaretskii
2022-12-05 15:06 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-05 15:40 ` Eli Zaretskii
2022-12-05 19:23 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-05 20:04 ` Eli Zaretskii
2022-12-05 20:07 ` Yuan Fu
2022-12-05 20:13 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-05 20:25 ` Yuan Fu
2022-12-05 20:27 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-06 5:41 ` Yuan Fu
2022-12-07 0:53 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-08 13:00 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors [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='VTid1_Y0Kc_pxoIErZhbUlB0fNG4mMO0tEQ3PgJz0u7SV-SjK1_ISSl9KhgYuO3AAUAUH04uomxEn6gm_Unl42NRDcu253iQFL2WJc1r0AA=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=59828-done@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=heimeborgia@protonmail.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).