unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Heime <heimeborgia@protonmail.com>
To: Jean Louis <bugs@gnu.support>
Cc: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: Re: Adding colour when font-lock in disabled
Date: Fri, 09 Dec 2022 23:19:17 +0000	[thread overview]
Message-ID: <7hfB2ezKjZh_K-reiMy_gBkdzzIdjPKMcgHK2dFD_JA8ISv5dWcSO2rNRm40ZKGFns3J-Gq0AfD4E6pPfSL03pgK56kDGuHzIUXO638yw9s=@protonmail.com> (raw)
In-Reply-To: <Y5OEcU/ScWU5R5Xc@protected.localdomain>


------- Original Message -------
On Friday, December 9th, 2022 at 6:54 PM, Jean Louis <bugs@gnu.support> wrote:


> * Heime heimeborgia@protonmail.com [2022-12-09 15:29]:
> 
> > 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 can use for their own configuration and design to display
> > to users, and which is not a programming mode ?
> 
> 
> Try enriched mode.
> 
> Open any .txt file, do M-x enriched-mode and save the file.
> 
> Use Edit, Text Properties and you can load file that will visually
> retain properties.
> 
> --
> Jean
> 
> Take action in Free Software Foundation campaigns:
> https://www.fsf.org/campaigns
> 
> In support of Richard M. Stallman
> https://stallmansupport.org/


Have tried (enriched-mode).  I then select some text and do "Edit - Text Properties - Background Colour - Other".  But nothing happens.



  parent reply	other threads:[~2022-12-09 23:19 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 [this message]
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
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='7hfB2ezKjZh_K-reiMy_gBkdzzIdjPKMcgHK2dFD_JA8ISv5dWcSO2rNRm40ZKGFns3J-Gq0AfD4E6pPfSL03pgK56kDGuHzIUXO638yw9s=@protonmail.com' \
    --to=heimeborgia@protonmail.com \
    --cc=bugs@gnu.support \
    --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).