From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jambunathan K Newsgroups: gmane.emacs.bugs Subject: bug#13686: hi-yellow vs. hi-lock-1 Date: Sat, 09 Mar 2013 08:17:47 +0530 Message-ID: <87ehfpb86k.fsf@gmail.com> References: <878v6vidh7.fsf@gmail.com> <7BC00EAA1AF8466D8F9C17B3CA4E82B8@us.oracle.com> <87bob65sbw.fsf@gmail.com> <87wqtkxspi.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1362797313 4630 80.91.229.3 (9 Mar 2013 02:48:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 9 Mar 2013 02:48:33 +0000 (UTC) Cc: David Koppelman , 13686@debbugs.gnu.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Mar 09 03:48:57 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UE9qC-0004EN-Gv for geb-bug-gnu-emacs@m.gmane.org; Sat, 09 Mar 2013 03:48:56 +0100 Original-Received: from localhost ([::1]:34356 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UE9pq-0002aV-Hf for geb-bug-gnu-emacs@m.gmane.org; Fri, 08 Mar 2013 21:48:34 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:36660) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UE9pi-0002WA-N6 for bug-gnu-emacs@gnu.org; Fri, 08 Mar 2013 21:48:31 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UE9pd-0004ol-H9 for bug-gnu-emacs@gnu.org; Fri, 08 Mar 2013 21:48:26 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:36354) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UE9pd-0004oh-DY for bug-gnu-emacs@gnu.org; Fri, 08 Mar 2013 21:48:21 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1UE9qH-0002XF-Hx for bug-gnu-emacs@gnu.org; Fri, 08 Mar 2013 21:49:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Jambunathan K Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 09 Mar 2013 02:49:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 13686 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 13686-submit@debbugs.gnu.org id=B13686.13627973179715 (code B ref 13686); Sat, 09 Mar 2013 02:49:01 +0000 Original-Received: (at 13686) by debbugs.gnu.org; 9 Mar 2013 02:48:37 +0000 Original-Received: from localhost ([127.0.0.1]:40463 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1UE9pt-0002Wc-7F for submit@debbugs.gnu.org; Fri, 08 Mar 2013 21:48:37 -0500 Original-Received: from mail-pb0-f49.google.com ([209.85.160.49]:53344) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1UE9pq-0002WQ-EL for 13686@debbugs.gnu.org; Fri, 08 Mar 2013 21:48:35 -0500 Original-Received: by mail-pb0-f49.google.com with SMTP id xa12so1811031pbc.8 for <13686@debbugs.gnu.org>; Fri, 08 Mar 2013 18:47:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-type; bh=8XB1kCRxJvvwmafVKkzj4VzOqTTgNm7PwzGqGy+CyU0=; b=eE7EC/xrG+0xiCRrheisygXilDCsR+grQb5gu5zJKKWNREfPCdzIMrH1ImWq6L5zxn EahZGShavzToEz6xQ/BTTJ4iARzgfbRa5QhrYdacuvr/yJ5FtZpU/SEj5IrFjlLGRaRR k2TeertY/CQLQQzLQn7FhiCmzqJbKFi/ONQ8ThcLYEgWhL3oN2GSKe/rF0r9BUysA/Yj B6dcQ3fO3Jh4UylHHfUcV8eHL207MsyD6KsGoeyGzrGZmslxDKyQSPghJY2ORlEtcNNY 9N7EM+pHrRNESUhGBp1tTdD5xb88FDsr+UZhdfUhHSo0EaanUnfxlpbrE+tt8XfYh6WM nk/w== X-Received: by 10.68.211.103 with SMTP id nb7mr7609307pbc.140.1362797267949; Fri, 08 Mar 2013 18:47:47 -0800 (PST) Original-Received: from debian-6.05 ([115.242.225.97]) by mx.google.com with ESMTPS id hs8sm7839027pbc.27.2013.03.08.18.47.44 (version=TLSv1.1 cipher=RC4-SHA bits=128/128); Fri, 08 Mar 2013 18:47:46 -0800 (PST) In-Reply-To: (Stefan Monnier's message of "Fri, 08 Mar 2013 20:33:15 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:72256 Archived-At: Stefan Monnier writes: >>> hi-lock-N >>> highlight-N >>> font-lock-user-N >>> font-lock-highlight-N >>> font-lock-extra-face-N > > The "font-lock-" names are due to history. There's no point using > this scheme for new faces, especially for faces not directly linked to > font-lock. David had reservations with introducing hi-lock-N. I am not sure he continues to hold this reservation. For now, highlight-Ns for N=6 with highlight and highlight-1 aliased to each other. >> As for the convention of not naming or otherwise linking a face with >> particular attributes (as some may interpret it), either it doesn't >> apply here, or if it does, it's a good place to ignore it. I've argued >> before that it does not apply because as most agree faces should be >> defined for a particular purpose rather than for appearance, such as >> for highlighting variable names. The face hi-yellow has a purpose: >> highlight something with a background of yellow. It is named >> appropriately and its attributes are so set. If there is a rule >> somewhere which clearly states that this is not allowed, then that >> rule should be broken in this case. > > How 'bout designing a concise "face description" format, so that instead > of choosing "hi-yellow", the user can choose (say) "b:yellow", > "f:blue", or "s:bold". This would give access to "any color", and in > order not to overwhelm the user, the completion would default to only > completing among a predefined set (corresponding to the current > predefined faces)? So you are steering the discussion exactly to the opposite extreme. What is your motivation here. Where do you think jit named-faces could be useful, apart from highlighting case. > Stefan