unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: scame via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "47313@debbugs.gnu.org" <47313@debbugs.gnu.org>
Subject: bug#47313: 27.1; highlight functions should accept colors too
Date: Mon, 22 Mar 2021 17:44:40 +0000	[thread overview]
Message-ID: <qvgMe2sLLY44MV0TTIcy1WnhKxXTphDYhGsr_CpmrIYB8xu8gC7ZFGwnbZmnte3vU5BdoFXI3SczK9ET9dkMbnSZN1ybLl4fZ-sG4cYAHoo=@protonmail.com> (raw)
In-Reply-To: <83v99j9jnu.fsf@gnu.org>

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

I thought people only used colors to temporarily highlight certain phrases,
etc. If it's not true then you have a point that faces can do more.

At least, the face completion prompt should be improved, so that it shows
the face's style inline like with list-faces-display.This could solve
the color selection problem, because if the face's style is instantly
visible then the user can simply choose a face which is similar to the
color he wants.








  reply	other threads:[~2021-03-22 17:44 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
2021-03-22 17:44   ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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='qvgMe2sLLY44MV0TTIcy1WnhKxXTphDYhGsr_CpmrIYB8xu8gC7ZFGwnbZmnte3vU5BdoFXI3SczK9ET9dkMbnSZN1ybLl4fZ-sG4cYAHoo=@protonmail.com' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=47313@debbugs.gnu.org \
    --cc=eliz@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).