all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 19877@debbugs.gnu.org
Subject: bug#19877: 24.4; highlight-regexp displays nonsense options for faces
Date: Thu, 19 Feb 2015 21:14:40 +0200	[thread overview]
Message-ID: <873861u31b.fsf@mail.linkov.net> (raw)
In-Reply-To: <54E52D3F.6090703@gmx.com> (Boruch Baum's message of "Wed, 18 Feb 2015 19:24:31 -0500")

>> Maybe the list of all faces (that come after the default faces)
>> should be better sorted somehow, e.g. alphabetically or by use frequency.
> My vote is to just restrict the options to those specified in
> hi-lock-face-defaults. The value can be easily modified, and its a
> simple way to keep unusual and unexpected faces from appearing.

Currently it's not too easy to modify since hi-lock-face-defaults
is defined with defvar, but not defcustom.

> Also, how many hi-lock faces is anyone going to ever need?

I'd say that in average 8 faces are needed, but the problem is
that hi-lock-face-defaults provides only 4 usable default faces
("hi-yellow" "hi-pink" "hi-green" "hi-blue").  The rest of
default faces with the prefix "-b" are highlighting with bold weight,
so they are less usable.  This is why often is necessary to find
more faces in the list of all faces that come after default faces.





  reply	other threads:[~2015-02-19 19:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15 18:32 bug#19877: 24.4; highlight-regexp displays nonsense options for faces Boruch Baum
2015-02-16 19:11 ` Glenn Morris
2015-02-17 15:25   ` bug#19876: " Boruch Baum
2015-02-17 16:56     ` Glenn Morris
2015-02-18 18:23 ` Juri Linkov
2015-02-19  0:24   ` Boruch Baum
2015-02-19 19:14     ` Juri Linkov [this message]
2015-02-19 21:41       ` Boruch Baum
2022-01-24 18:52 ` Lars Ingebrigtsen
2022-01-24 19:08   ` Juri Linkov
2022-01-24 19:11     ` 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=873861u31b.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=19877@debbugs.gnu.org \
    --cc=boruch_baum@gmx.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.