From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: emacs-devel@gnu.org
Subject: Re: f90 problem
Date: Sun, 31 Mar 2002 20:58:38 -0500 [thread overview]
Message-ID: <200204010158.g311wcp12032@rum.cs.yale.edu> (raw)
In-Reply-To: 200203300345.g2U3j3Q10370@aztec.santafe.edu
> Would anyone like to work on this?
[...]
> > The reformatting is inconsistent between region indentation
> > (meta-ctrl-Q) and the use of tab on an individual line, when
> > formatting a multi-line variable declaration which includes
> > comments. For example, indent-region yields the following:
[...]
> > The two are inconsistent. The tab behavior is the correct behavior.
I'm willing to work on this, but my solution might not be to
everybody's taste:
Remove f90-indent-region and set indent-region-function to nil,
-- Stefan
prev parent reply other threads:[~2002-04-01 1:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-30 3:45 f90 problem Richard Stallman
2002-04-01 1:58 ` Stefan Monnier [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
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=200204010158.g311wcp12032@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=emacs-devel@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 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).