From: Glenn Morris <rgm+news@stanford.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: Fortran (95/03) syntax highlighting
Date: Wed, 20 Aug 2008 09:46:51 -0700 [thread overview]
Message-ID: <8g63pvocqs.fsf@xoc2.stanford.edu> (raw)
In-Reply-To: mailman.17124.1219225804.18990.help-gnu-emacs@gnu.org
Nikolaj Schumacher wrote:
> "Izaak Beekman" <ibeekman@princeton.edu> wrote:
>
>> 2) No support for Fortran 03 syntax
>
> It's currently not supported by Emacs. You could look for an
> external package, but I wouldn't get my hopes up.
The development version of Emacs (to be released as 23.1 hopefully on
the order of six months) has supported F03 for the best part of a year.
I encourage people to try it out and report any problems or missing
features.
>> 1) Incorrect syntax highlighting in variable declarations with line
>> continuations.
>
> If that's legal F95 syntax, I'd report it as a bug. (M-x report-emacs-bug)
Indeed.
>> 3) .f95 and .f03 file-name-suffixes are not recognized.
.f95 was in Emacs 22.1 (added to CVS over six years ago), released over
a year ago. There is no reason to use anything other than 22.2 nowadays
(22.3 coming soonish).
I have not added .f03 because it is my understanding that the adoption
of .f95 as an extension was basically a mistake, and that we were never
intended to change the name of our files every few years. Can't remember
where I got this idea from, pointers to corrections saying that .f03 is
a recommended extension are welcome.
prev parent reply other threads:[~2008-08-20 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 20:11 Fortran (95/03) syntax highlighting Izaak Beekman
2008-08-20 9:50 ` Nikolaj Schumacher
2008-08-20 17:01 ` Izaak Beekman
[not found] ` <mailman.17166.1219251721.18990.help-gnu-emacs@gnu.org>
2008-08-20 17:05 ` Glenn Morris
[not found] ` <mailman.17124.1219225804.18990.help-gnu-emacs@gnu.org>
2008-08-20 16:46 ` Glenn Morris [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8g63pvocqs.fsf@xoc2.stanford.edu \
--to=rgm+news@stanford.edu \
--cc=help-gnu-emacs@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.