From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 14448@debbugs.gnu.org, Angelo Graziosi <angelo.graziosi@alice.it>
Subject: bug#14448: Wrong indentation in comment lines for F90 mode?
Date: Sat, 25 May 2013 23:09:03 -0400 [thread overview]
Message-ID: <ofobbye8ts.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwv8v33iwmc.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 24 May 2013 23:23:27 -0400")
Stefan Monnier wrote:
> I see now that it behaves differently because f90 tells it to, via
> f90-comment-indent. Try:
>
> ! bla
> ! bli
>
> and then hit either TAB or M-; on the second line, and you'll see it
> gets indented by 1 more space, just like in your example.
ITYM 2 spaces?
This takes me back to my original question:
Is M-j supposed to re-indent the line it starts on, or not?
If not, is it supposed to indent the following line as it would normally
be indented, or to match the indentation of the original line?
If the answers are "no", and "as normal", then there is no bug here.
> It seems that this happens only for comments before source code...
Probably because that is an ambiguous state, depending on whether or not
a leading "program" line gets added. See
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3729#10
next prev parent reply other threads:[~2013-05-26 3:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 10:51 bug#14448: Wrong indentation in comment lines for F90 mode? Angelo Graziosi
2013-05-23 17:04 ` Glenn Morris
2013-05-23 20:00 ` Angelo Graziosi
2013-05-25 3:23 ` Stefan Monnier
2013-05-25 11:24 ` Angelo Graziosi
2013-05-26 3:09 ` Glenn Morris [this message]
2013-05-26 18:36 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2010-02-18 10:30 bug#5595: Commenting in F90 Angelo Graziosi
2022-02-05 23:44 ` bug#14448: Wrong indentation in comment lines for F90 mode? Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ofobbye8ts.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=14448@debbugs.gnu.org \
--cc=angelo.graziosi@alice.it \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).