all messages for Emacs-related lists mirrored at yhetil.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 18:39:11 +0000	[thread overview]
Message-ID: <F5t0kPzDUF1G5kNDtMaTLg2wvhr4_zAEQlj109JCb6j8EDfVmTXztvfun7duLAeCIDD9PDcgDNa2w8eTslaOOgONDaNMtpc1ddZjI7vuwm4=@protonmail.com> (raw)
In-Reply-To: <83h7l39i5q.fsf@gnu.org>


>
> We could try that, but I fear that the result of showing many faces in
> the same buffer one besides the other will look ugly, while displaying
> them one face per line would make a very long buffer, scrolling
> through which could be impractical.

It can't be uglier than the completions of read-color which is pretty bad.
It's a cacophony of colors and some of them are hard to read:

https://i.imgur.com/NtIDihs.png

IMO the list-colors-display UI is much better even if it's longer (and if
it's a completion list then it's easy to narrow it down):

https://www.valenciatech.com/wp-content/uploads/2019/08/gnu-emacs-list-colors-display.png





  reply	other threads:[~2021-03-22 18:39 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='F5t0kPzDUF1G5kNDtMaTLg2wvhr4_zAEQlj109JCb6j8EDfVmTXztvfun7duLAeCIDD9PDcgDNa2w8eTslaOOgONDaNMtpc1ddZjI7vuwm4=@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.