unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: scame <laszlomail@protonmail.com>
Cc: 47313@debbugs.gnu.org
Subject: bug#47313: 27.1; highlight functions should accept colors too
Date: Mon, 22 Mar 2021 19:34:45 +0200	[thread overview]
Message-ID: <83v99j9jnu.fsf@gnu.org> (raw)
In-Reply-To: <9Z87HwaBASS5vyB3il_aT_xphTn0UzaFsdlKvuDcPwWwUIUcwhJJj2Kv1tLFasLle8mPX2Rgo9KQ3Xo4KwsK6WqkGG5wRNKGwyXGiwPrg9M=@protonmail.com> (bug-gnu-emacs@gnu.org)

> Date: Mon, 22 Mar 2021 09:29:24 +0000
> From:  scame via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> I wanted to use highlight-regexp to color some lines gray, but the command
> did not accept the color, it only accept faces, so I had to look for a suitable
> face.
> 
> These highlight-* commands should accept color names too if the user
> wants a specific color, not a specific face,

Faces are not just colors, they have many additional attributes.

I'm not sure it is a good idea to make these commands accept both
faces and colors, as this could make the UI confusing and error prone.
It may be better to provide new commands, similar to the existing
ones, but which will accept only the colors instead of faces.

(You could of course define a face which specifies just the color, and
use that with highlight-* commands, but that is less user-friendly.)





  reply	other threads:[~2021-03-22 17:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22  9:29 bug#47313: 27.1; highlight functions should accept colors too scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-22 17:34 ` Eli Zaretskii [this message]
2021-03-22 17:44   ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-22 18:07     ` Eli Zaretskii
2021-03-22 18:39       ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-22 19:01         ` Eli Zaretskii
2021-03-22 18:53     ` Lars Ingebrigtsen

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=83v99j9jnu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=47313@debbugs.gnu.org \
    --cc=laszlomail@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).