GNU bug report logs - #17895
24.3.91; electric-indent-mode not quite right with comments in fortran-mode

Previous Next

Package: emacs;

Reported by: "Roland Winkler" <winkler <at> gnu.org>

Date: Tue, 1 Jul 2014 21:32:01 UTC

Severity: minor

Tags: wontfix

Found in version 24.3.91

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #17 received at 17895 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Glenn Morris <rgm <at> gnu.org>
Cc: Roland Winkler <winkler <at> gnu.org>, 17895 <at> debbugs.gnu.org
Subject: Re: bug#17895: 24.3.91;
 electric-indent-mode not quite right with comments in fortran-mode
Date: Tue, 01 Jul 2014 21:17:47 -0400
> Other modes, such as Python, have similar issues.

Actually, I think it's different: the problem with Python is that even
once the line is fully written, python-mode can't always decide where to
indent it, because there are several valid choices (and they don't mean
the same thing).

Instead, the problem here seems to only affect empty lines (i.e. lines
where the text hasn't been written yet), and this problem affects
many/most modes.

But I guess if the first non-whitespace char is a capital C,
fortran-mode has a similar problem to python-mode in that it can't know
for sure if the line should be assumed to be a comment (and go to
column-0) or to be some instruction that happens to start with a capital
C (and should go to some further column).

> or: RET $ TAB

And adding $ to electric-indent-chars would even save you from typing
this TAB (which doesn't mean that's what fortran-mode should do, tho.
I have the impression that this kind of old-style Fortran is fairly rare
nowadays).


        Stefan




This bug report was last modified 9 years and 81 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.