From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: 17620@debbugs.gnu.org
Subject: bug#17620: sh-mode indentation of continued do loop lists
Date: Wed, 28 May 2014 22:23:50 -0400 [thread overview]
Message-ID: <jwvfvjtl4ij.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <qb1tvd1tok.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 28 May 2014 17:26:19 -0400")
> In 24.3.91, the continued line gets way too much indentation:
> for foo in a \
> b; do
> echo $foo
> done
I think this requires a config variable:
- The indentation you show above is the one that makes sense to me,
where the \ is just a way to write "a b" on multiple logical lines,
like you can do in most free-form programming languages, in which case
"b", being an argument to "a", should be indented a bit deeper than
"a". I.e. the indentation rule pretends the \ don't really exist.
- The indentation you ask for seems to be based on the idea that "\" is
a way to split a single logical line into several physical lines,
doing a kind of manual "word wrap".
IOW the first view would want
for f in a; do \
for g in b; do \
echo toto; \
done; \
done
[ tho I see now that the current code fails here (probably because it
doesn't understand that the "do"s are "hanging"). ]
whereas the second view would want
for f in a; do \
for g in b; do \
echo toto; \
done; \
done
I don't see a way to reconcile those two views, hence the need for
a config variable to choose between those two schools.
Stefan
next prev parent reply other threads:[~2014-05-29 2:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 21:26 bug#17620: sh-mode indentation of continued do loop lists Glenn Morris
2014-05-29 2:23 ` Stefan Monnier [this message]
2014-05-29 3:06 ` Glenn Morris
2015-09-30 1:46 ` Stefan Monnier
2015-02-18 19:11 ` Philipp Stephani
2015-02-18 19:18 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvfvjtl4ij.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=17620@debbugs.gnu.org \
--cc=rgm@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.