GNU bug report logs -
#20985
Bug in fortran fixed format mode with lines longer than 72 characters
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 20985 in the body.
You can then email your comments to 20985 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#20985
; Package
emacs
.
(Sun, 05 Jul 2015 17:36:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Mark van Schilfgaarde <mark.vanschilfgaarde <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sun, 05 Jul 2015 17:36:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
I am reporting a bug in emacs version 24.5.1. It appears both on a
mac an on a linux machine.
Some functions in fortran fixed-format mode, with lines exceeding 72
columns (132 for example), still assume a 72 column width, independent
of the value of variable fortran-line-length
In particular sexp operations like (forward-sexp) assume characters
past 72 columns are comments.
Consider the attached "example.f" : Read the file with
emacs -Q example.f
Change variable fortran-line-length :
(set-variable (quote fortran-line-length) 132 nil)
so that now:
(describe-variable (quote fortran-line-length))
returns:
fortran-line-length is a variable defined in `fortran.el'.
Its value is 132
Original value was 72
Local in buffer example.f; global value is 72
Move the point just after test1, so it precedes the first expression (..).
In this case forward-sexp works as expected.
Move the point just after test2, so it precedes the second expression (..).
In this case forward-sexp fails to find the end of the expression.
Note also that "twelve)" is highlighted as though it is a comment.
This problem does not appear in emacs 21.4
--
Professor Mark van Schilfgaarde Tel. +44 (0)207 848 7246
Department of Physics Fax. +44 (0)20 7848 2420
King's College London e-mail:
Mark.vanSchilfgaarde <at> gmail.com
Strand, London WC2R 2LS, UK http://www.kcl.ac.uk/physics
[example.f (application/octet-stream, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#20985
; Package
emacs
.
(Mon, 06 Jul 2015 00:01:03 GMT)
Full text and
rfc822 format available.
Message #8 received at 20985 <at> debbugs.gnu.org (full text, mbox):
Mark van Schilfgaarde wrote:
> (set-variable (quote fortran-line-length) 132 nil)
Thanks for the report. However, as it says in
C-h v fortran-line-length
Setting this variable directly (after fortran mode is loaded) does
not take effect. Use either M-x customize (which affects all Fortran
buffers and the default) or the function `fortran-line-length'
(which can also operate on just the current buffer).
So: use
C-u 132 M-x fortran-line-length
> This problem does not appear in emacs 21.4
The variable fortran-line-length does not exist in 21.4.
Added tag(s) notabug.
Request was from
Glenn Morris <rgm <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Mon, 06 Jul 2015 00:23:01 GMT)
Full text and
rfc822 format available.
bug closed, send any further explanations to
20985 <at> debbugs.gnu.org and Mark van Schilfgaarde <mark.vanschilfgaarde <at> gmail.com>
Request was from
Glenn Morris <rgm <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Mon, 06 Jul 2015 00:23:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 03 Aug 2015 11:24:07 GMT)
Full text and
rfc822 format available.
This bug report was last modified 10 years and 17 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.