unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuan Fu <casouri@gmail.com>
To: Heime <heimeborgia@protonmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 59828-done@debbugs.gnu.org
Subject: bug#59828: Fundamental Mode buffers fail to keep text properties
Date: Mon, 5 Dec 2022 21:41:23 -0800	[thread overview]
Message-ID: <6626BA91-D7E0-4AEC-9897-4220F96C143D@gmail.com> (raw)
In-Reply-To: <ANmuMxexwFrexWE6jQ90ieFaTAioy7FjDR_ZDAZmLH8-5fyTa_mYXvH2WTLCvfwPuGhIdQYypbNvt_yL-M83zwPD6ZfixZ01AX9gvfNrD5I=@protonmail.com>

>>> 
>>> 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




  reply	other threads:[~2022-12-06  5:41 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 [this message]
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

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=6626BA91-D7E0-4AEC-9897-4220F96C143D@gmail.com \
    --to=casouri@gmail.com \
    --cc=59828-done@debbugs.gnu.org \
    --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).