From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "lutorm" Newsgroups: gmane.emacs.help Subject: Re: Matching of template <> in C++ mode Date: 20 Feb 2007 11:57:51 -0800 Organization: http://groups.google.com Message-ID: <1172001471.724420.133110@k78g2000cwa.googlegroups.com> References: <1171932366.467171.188610@h3g2000cwc.googlegroups.com> <1171976649.747936.9130@h3g2000cwc.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Trace: sea.gmane.org 1172004082 1014 80.91.229.12 (20 Feb 2007 20:41:22 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 20 Feb 2007 20:41:22 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Feb 20 21:41:15 2007 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HJbnU-00057Y-Hr for geh-help-gnu-emacs@m.gmane.org; Tue, 20 Feb 2007 21:41:12 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HJbnU-0006SF-1I for geh-help-gnu-emacs@m.gmane.org; Tue, 20 Feb 2007 15:41:12 -0500 Original-Path: shelby.stanford.edu!headwall.stanford.edu!newshub.sdsu.edu!postnews.google.com!k78g2000cwa.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 19 Original-NNTP-Posting-Host: 63.249.107.95 Original-X-Trace: posting.google.com 1172001485 3930 127.0.0.1 (20 Feb 2007 19:58:05 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Tue, 20 Feb 2007 19:58:05 +0000 (UTC) In-Reply-To: <1171976649.747936.9130@h3g2000cwc.googlegroups.com> User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.9) Gecko/20061206 Firefox/1.5.0.9,gzip(gfe),gzip(gfe) Complaints-To: groups-abuse@google.com Injection-Info: k78g2000cwa.googlegroups.com; posting-host=63.249.107.95; posting-account=N4FzmwwAAABqc2oEMxcOa-m_5k2ufq7Q Original-Xref: shelby.stanford.edu gnu.emacs.help:145754 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:41359 Archived-At: On Feb 20, 5:04 am, "rgb" wrote: > Actually it would totally wreck real paren class matching. > The characters < and > are typically used all over and if > they had paren syntax then the parens in (x > y) would not > match any more. The implementation would need to be careful > not to give < or > characters paren syntax except under the > specific template conditions you've described. Yeah, you're right. I guess I'm thinking of it as two separate functions, the blinking of matching parens and the determining if they are mismatched. It would still be useful if it would blink matching pairs of <> even if doing nothing else. However, this is not a new problem, it already has to figure out if a paren character is in a string or comment. I was going to say that the syntax highlighting has to have solved it, too, but upon closer inspection it has not... Anyway, it seems the number of people writing C++ with emacs must be pretty large so I can't be the first one to think of this?