From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Glenn Morris Newsgroups: gmane.emacs.bugs Subject: f90-mode [was Re: How to update major modes?] Date: Thu, 25 Oct 2007 00:10:20 -0400 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1193285482 13567 80.91.229.12 (25 Oct 2007 04:11:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 25 Oct 2007 04:11:22 +0000 (UTC) Cc: bug-gnu-emacs@gnu.org To: Jared Ahern Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Oct 25 06:11:23 2007 Return-path: Envelope-to: geb-bug-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 1Iku40-00025O-9I for geb-bug-gnu-emacs@m.gmane.org; Thu, 25 Oct 2007 06:11:20 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Iku3r-0006fT-Un for geb-bug-gnu-emacs@m.gmane.org; Thu, 25 Oct 2007 00:11:11 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Iku34-0006DC-CF for bug-gnu-emacs@gnu.org; Thu, 25 Oct 2007 00:10:22 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Iku33-0006CM-I7 for bug-gnu-emacs@gnu.org; Thu, 25 Oct 2007 00:10:21 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Iku33-0006C6-BK for bug-gnu-emacs@gnu.org; Thu, 25 Oct 2007 00:10:21 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Iku32-00066k-Vw for bug-gnu-emacs@gnu.org; Thu, 25 Oct 2007 00:10:21 -0400 Original-Received: from rgm by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1Iku32-0001w2-Nr; Thu, 25 Oct 2007 00:10:20 -0400 X-Spook: passwd Belknap blackjack Europol Project Monarch Aladdin X-Ran: (.z5Vop74f*Rnhktkb)!(&Ih6=^J^'6>}hwfYw*_1_l?>vAV7G)0zchEAi0ZM#h.w0bbHb X-Hue: green X-Attribution: GM User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:16828 Archived-At: Jared Ahern wrote: > 1) On initialization expressions, all of the stuff on the RHS of the > '=' sign are in the same color It's always worked like that, and I don't think I'd want to change this. > 2) DEFAULT when it follows CASE is a keyword, or close enough That would be easy to change, but it's always been the way it is. > 3) ... same with IN/OUT/INOUT in INTENT() expressions Same as previous. I think 2) and 3) are really things for your .emacs file. > 4) Syntax coloring may fail across lines continued with '&' Sure, you can always write the code in such a way as to fool font-locking. Trying to support statements split over lines would be a lot of extra work for little gain, IMO. > 5) TYPE(...) declarations are now hilited (great!), but this is done > differently than REAL() and INTEGER(); I'd much prefer this over > nothing, so not a huge deal. You mean in something like: type(sometype) :: foo you would prefer only the "type" part to be highlighted, not the whole "type(sometype)"? Yes, I wondered about this too. It would in some sense be more consistent with something "integer(kind=foo)" and is easy to do. But the way it works now is how it was originally supposed to work, until some typo crept in and broke it at some point. > 6) INTRINSIC (and NON_INTRINSIC ?) kills the rest of the normal > syntax hiliting on a USE statement; Should be fixed now. > I don't mean to make demands or anything. Not at all. It's nice to get some feedback. > On a side note, in TeX-mode, you can insert '\end{...whatever...}' > with C-C C-E, much like typing 'END' and then TAB in F90. How would > I bind the latter to the former's key combo in my .emacs? I guess you want: (defun my-f90-mode-hook () (local-set-key "\C-c\C-e" 'f90-match-end)) (add-hook 'f90-mode-hook 'my-f90-mode-hook)