unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Angelo Graziosi <angelo.graziosi@alice.it>
Cc: 14448@debbugs.gnu.org
Subject: bug#14448: Wrong indentation in comment lines for F90 mode?
Date: Fri, 24 May 2013 23:23:27 -0400	[thread overview]
Message-ID: <jwv8v33iwmc.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <519E754D.1030405@alice.it> (Angelo Graziosi's message of "Thu, 23 May 2013 22:00:13 +0200")

>> I don't understand what comment-indent-new-line is supposed to do, nor
>> which variables modes should set to make it work correctly.

To tell you the truth, I don't know either.  The way I see it, M-j
should be bound to a function that funcalls comment-line-break-function
(whose default value is comment-indent-new-line).  So modes can modify
comment-line-break-function (ideally via add-function) to tune
its behavior.

> F90 is a "free text style of languages and comments" like C++, so one
> doesn't understand why its comments behaves differently...

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.


        Stefan





  reply	other threads:[~2013-05-25  3:23 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 [this message]
2013-05-25 11:24       ` Angelo Graziosi
2013-05-26  3:09       ` Glenn Morris
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=jwv8v33iwmc.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=14448@debbugs.gnu.org \
    --cc=angelo.graziosi@alice.it \
    /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).