From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daniel Brockman Newsgroups: gmane.emacs.devel Subject: Re: regexp font-lock highlighting Date: Tue, 31 May 2005 04:45:55 +0200 Message-ID: <87sm043yfw.fsf@wigwam.deepwood.net> References: <429AD1B5.1020408@gmx.at> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1117509406 5075 80.91.229.2 (31 May 2005 03:16:46 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 May 2005 03:16:46 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 31 05:16:43 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DcxEw-0005d8-LE for ged-emacs-devel@m.gmane.org; Tue, 31 May 2005 05:16:26 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DcxJw-0004J9-Tx for ged-emacs-devel@m.gmane.org; Mon, 30 May 2005 23:21:37 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DcxGW-0002dJ-Pw for emacs-devel@gnu.org; Mon, 30 May 2005 23:18:05 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DcxGV-0002cP-RP for emacs-devel@gnu.org; Mon, 30 May 2005 23:18:04 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DcxFy-0001ng-Al for emacs-devel@gnu.org; Mon, 30 May 2005 23:17:30 -0400 Original-Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtp (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.34) id 1DcwmO-00014s-Cv for emacs-devel@gnu.org; Mon, 30 May 2005 22:46:56 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Dcwhb-0002zW-GY for emacs-devel@gnu.org; Tue, 31 May 2005 04:41:59 +0200 Original-Received: from c-4fb670d5.028-10-67766c2.cust.bredbandsbolaget.se ([213.112.182.79]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 31 May 2005 04:41:59 +0200 Original-Received: from daniel by c-4fb670d5.028-10-67766c2.cust.bredbandsbolaget.se with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 31 May 2005 04:41:59 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 36 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: c-4fb670d5.028-10-67766c2.cust.bredbandsbolaget.se X-Face: :&2UWGm>e24)ip~'K@iOsA&JT3JX*v@1-#L)=dUb825\Fwg#`^N!Y*g-TqdS AevzjFJe96f@V'ya8${57/T'"mTd`1o{TGYhHnVucLq!D$r2O{IN)7>.0op_Y`%r;/Q +(]`3F-t10N7NF\.Mm0q}p1:%iqTi:5]1E]rDF)R$9.!,Eu'9K':y9^U3F8UCS1M+A$ 8[[[WT^`$P[vu>P+8]aQMh9giu&fPCqLW2FSsGs User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) Cancel-Lock: sha1:LTA8Cl6KQfAOGZ9nJkAEl4+l8xY= X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:37916 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:37916 martin rudalics writes: > The recent modification of `lisp-font-lock-keywords-2' to highlight > subexpressions of regexps has two minor bugs: [...] > Finally, I would use three distinct font-lock faces for regexps: FWIW, I wholeheartedly agree. > - One face for highlighting the "\\"s which by default should > inherit from `font-lock-string-face' with a dimmed foreground - > I'm using Green4 for strings and PaleGreen3 for the "\\"s. That's exactly what I would like to do. > Anyone who doesn't like the highlighting could revert to > `font-lock-string-face'. > - One face for highlighting the "(", "|" and ")" in these > expressions. I find `bold' good here but again would leave it to > the user whether she wants to turn off highlighting this. > Moreover, such a face could allow paren-highlighting to _never_ > match a paren with that face with a paren with another face. > Consequently, paren-matching could finally provide more trustable > information within regular expressions. That would be awesome. I'm sorry, I don't have anything to add. I just felt the need to support this suggestion. I have been thinking along the same lines, only not as well as Martin has. :-) -- Daniel Brockman