From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Heime Newsgroups: gmane.emacs.help Subject: Re: Adding colour when font-lock in disabled Date: Fri, 09 Dec 2022 12:27:22 +0000 Message-ID: References: <838rjh12ar.fsf@gnu.org> <831qp82340.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33722"; mail-complaints-to="usenet@ciao.gmane.io" Cc: help-gnu-emacs@gnu.org To: Eli Zaretskii Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Fri Dec 09 13:28:46 2022 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p3cUf-0008ZW-F5 for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 09 Dec 2022 13:28:45 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p3cTm-0007ja-4y; Fri, 09 Dec 2022 07:27:50 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p3cTi-0007jI-K4 for help-gnu-emacs@gnu.org; Fri, 09 Dec 2022 07:27:47 -0500 Original-Received: from mail-4324.protonmail.ch ([185.70.43.24]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p3cTU-0007yt-3e for help-gnu-emacs@gnu.org; Fri, 09 Dec 2022 07:27:39 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1670588849; x=1670848049; bh=lHQ0wmpoVfSmHSAl+srCaLsvAuuAB8+Y22to7YKGP2A=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=zjI5XTCznvj3OHMmtCYiS/CW4jWk1FQ7YDNJ+FXcb6CDOzphzFz1/C8QahfUQamoP GSWynHBoI+yr6FuYuFjVt83VeWvmBgajtVswDqC7yBkj+aSicElKAM/IFFCZxwz9qo mzVCHDlWWq7ff0a5UWucbOfp+u22Xwueuh7285qX/N9Y1nPkQKqLdGR5CX+Qm/A9aV LzY+c0vGMA0L0aTq6nnNKuE1wdk18b9MvZ97U9TSmRJWDxU6bdwSp5NpBchx6TR1QL jdZUfLPVOWhxg7KBXRufozgiMfF/R1FnbFWtxyTyl+6t+kc9ePdPAwQ+VJY9YH2+ot ZXjejtXZk3KMQ== In-Reply-To: <831qp82340.fsf@gnu.org> Feedback-ID: 57735886:user:proton Received-SPF: pass client-ip=185.70.43.24; envelope-from=heimeborgia@protonmail.com; helo=mail-4324.protonmail.ch X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:141506 Archived-At: ------- Original Message ------- On Friday, December 9th, 2022 at 12:06 PM, Eli Zaretskii wro= te: > > Date: Fri, 09 Dec 2022 08:09:08 +0000 > > From: Heime heimeborgia@protonmail.com > > Cc: help-gnu-emacs@gnu.org > >=20 > > > 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. > >=20 > > But them when a user wants to introduce some text with some properties = (e.g. colour), what is supposed to do. >=20 >=20 > Users aren't supposed to introduce text properties, except via Lisp > programs. >=20 > > Would you expect someone to use font-lock-face when font-lock is enable= d > >=20 > > (propertize "G" 'font-lock-face '(:foreground "green")) > >=20 > > -------- > >=20 > > And use > >=20 > > (propertize "G" 'face '(:foreground "green")) > >=20 > > when font lock is disabled. As a developer, what if I do not want font-lock to change it. Consider I make a special text file where I need to setup same sections in specific colours. Is there some special mode that developers c= an use for their own configuration and design to display to users, and whic= h is not a programming mode ? =20 What is the procedure in case there is font-lock enabled or font-lock disab= led ?=20 =20 Should I use an if condition to test for both, as above ? > The Lisp program which allows users to add faces should do something > like that, yes. >=20 > > Why places face properties according to the mode's definitions but not = allow us to change the properties of inserted text, when we can do that any= way? >=20 >=20 > Because font-lock must be in full control of face property to support > the situation where the user edits the text, and as result the faces > should change (e.g., because something that was previously just text > became a comment or a string, or vice versa). Right. =20 > > After calling a particular mode definitions, I should be able te change= properties rather than having a lock. >=20 > See above: the faces change dynamically to follow editing of the > buffer text. It is not a one-time operation. What if I try to do something different. Making a buffer for a package whe= re users are not expected to change it. For instance, a package could make= a named buffer that logs some operations, with certain things coloured. T= he faces would not change dynamically because users cannot edit the buffer = text. > If a user wants to highlight addition portions of the buffer, the > user-level feature we provide is hi-lock-mode (a minor mode). It > solves the complexity under the hood, and only requires the user to > specify the patterns to highlight. So if you want an easy user-level > interface, I suggest to use that minor mode.