unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Fred Krogh <fkrogh@mathalacarte.com>
Cc: 8944@debbugs.gnu.org
Subject: bug#8944: 23.3; Formatting of Labeled Constructs in Fortran
Date: Tue, 28 Jun 2011 17:24:11 -0400	[thread overview]
Message-ID: <19978.18043.878536.411684@fencepost.gnu.org> (raw)
In-Reply-To: <4E095C50.9090101@mathalacarte.com>


(Please keep the debbugs address included in replies).

Fred Krogh wrote (on Mon, 27 Jun 2011 at 21:45 -0700):

> > I don't understand what you are asking for, because the names
> > already make no difference to the indentation of subsequent lines.
[...]
> I must apologize.  I swear that this sort of thing was not working for
> me in the past.  I just tried your example and then a slightly more
> complicated example and it seems to work.

OK, good, that was easy!

> > I'm not going to implement this. It is too difficult to support
> > constructs split across lines.
> I'm sorry to belabor this.  Not knowing how this sort of think might
> actually be implemented it seems to me easy to ignore the indentation of
> a construct name.  Of course I really don't understand how this sort of
> thing gets handled and I am very grateful to have what I have.

The reason it makes life more difficult is that if everything is on
one line, you can basically just do everything with a simple regular
expression; but if things are allowed to be split over lines then
you need to do a more complicating parsing.

Anyway, I'll leave this bug report open but will mark it as "wontfix".





  parent reply	other threads:[~2011-06-28 21:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 19:24 bug#8944: 23.3; Formatting of Labeled Constructs in Fortran fkrogh
2011-06-28  1:42 ` Glenn Morris
     [not found]   ` <4E095C50.9090101@mathalacarte.com>
2011-06-28 21:24     ` Glenn Morris [this message]
2016-12-07 17:54       ` Glenn Morris

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=19978.18043.878536.411684@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=8944@debbugs.gnu.org \
    --cc=fkrogh@mathalacarte.com \
    /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).