unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: David Koppelman <koppel@ece.lsu.edu>
Cc: 13686@debbugs.gnu.org
Subject: bug#13686: hi-yellow vs. hi-lock-1
Date: Thu, 07 Mar 2013 01:36:50 +0530	[thread overview]
Message-ID: <87k3pkz411.fsf@gmail.com> (raw)
In-Reply-To: <yg5sj48b8wf.fsf@sky.ece.lsu.edu> (David Koppelman's message of "Wed, 06 Mar 2013 13:55:28 -0600")

David Koppelman <koppel@ece.lsu.edu> writes:

>> From: Jambunathan K <kjambunathan <at> gmail.com>
>>
>> Let's focus on core, themable faces.  How many you want in what prefix
>> or file.  I propose that these faces be named opaquely as
>
>>         hi-lock-N
>>         highlight-N
>>         font-lock-user-N
>>         font-lock-highlight-N
>>         font-lock-extra-face-N
>
> I object to using cryptic names for faces. 

Ok, I withdraw hi-lock-N.  As for other faces, I believe it is Stefan's
or Emacs maintainers call.  I am moving forward, after getting a
in-principle go from Stefan.

> The user should see a recognizable color name for the default hi-lock
> faces, and should be able to pick any face he or she likes. Hi-lock
> currently does this. I know that this can be achieved using face names
> such as hi-lock-1 by extracting a color from a face definition (if
> necessary, mapping an RGB triple to a name), but this is an
> unnecessary complication. As I see it, the only things that will be
> achieved are providing for themability and abiding by a convention
> that some interpret as a separation of face attributes from face
> names.

I gave a code snippet at the end of the mail.  If you had looked at it,
you will realize that I have done nothing which changes the status quo
but I have done eveything to accommodate my requirements.  I am the
proposer, right?

Please provide specific feedback on the snippet rather than registering
a broad objection.  I have made an effort to understand the
"I-want-color" camp and I have also openly acknowledged that the
"I-want-color" camp have valid and sensible arguments.

Jambunathan K.





  reply	other threads:[~2013-03-06 20:06 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11  6:14 bug#13686: 24.3.50; Re-look hi-lock-face-defaults (aka Provide more "core" faces for highlighting) Jambunathan K
2013-02-15 15:03 ` Stefan Monnier
2013-02-15 18:29   ` David Koppelman
2013-02-15 20:39     ` Stefan Monnier
2013-02-26 23:11 ` bug#13686: hi-yellow vs. hi-lock-1 David Koppelman
2013-02-27  0:33   ` Drew Adams
2013-02-27  1:35     ` Stefan Monnier
2013-02-27  3:59       ` Jambunathan K
2013-02-27  4:58       ` Drew Adams
2013-02-27  5:10         ` Jambunathan K
2013-02-27  5:38           ` Drew Adams
2013-02-27  5:54             ` Jambunathan K
2013-02-27  6:01               ` Drew Adams
2013-02-27 23:45             ` Juri Linkov
2013-03-06 18:43               ` Jambunathan K
2013-03-06 19:54                 ` David Koppelman
2013-03-07  9:16                 ` Juri Linkov
2013-03-06 19:04             ` Jambunathan K
2013-02-27  3:49     ` Jambunathan K
2013-02-27 13:46       ` Stefan Monnier
2013-02-27 14:56         ` Jambunathan K
2013-02-27 16:27           ` Stefan Monnier
2013-03-06 18:56         ` Jambunathan K
2013-03-06 19:55           ` David Koppelman
2013-03-06 20:06             ` Jambunathan K [this message]
2013-03-07  0:54               ` David Koppelman
2013-03-07  3:23                 ` Jambunathan K
2013-03-09  1:33             ` Stefan Monnier
2013-03-09  2:47               ` Jambunathan K
2013-03-09  3:26                 ` Stefan Monnier
2013-04-08  5:31               ` Jambunathan K
2013-04-10  4:11                 ` Jambunathan K
2013-04-10 18:33                 ` David Koppelman
2013-04-11  4:24                   ` Jambunathan K
2013-02-27  3:36   ` Jambunathan K
2013-02-27  4:08   ` Jambunathan K
2013-11-15  4:45 ` bug#13686: 24.3.50; Re-look hi-lock-face-defaults (aka Provide more "core" faces for highlighting) Jambunathan K

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=87k3pkz411.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=13686@debbugs.gnu.org \
    --cc=koppel@ece.lsu.edu \
    /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).