From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Debugging SMIE for sh-script.el
Date: Mon, 06 Sep 2021 10:01:56 -0400 [thread overview]
Message-ID: <jwva6kp959g.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <5542c259-2e3d-ce97-12ea-5e03d5c150a5@gmail.com> (Nikolay Kudryavtsev's message of "Mon, 6 Sep 2021 15:47:47 +0300")
>> indent the subsequent lines at a fixed offset from the first line
> The key question here is how do we calculate that offset.
No. The rule "indent the subsequent lines at a fixed offset from the
first line" is the one used when `sh-indent-after-continuation` is set
to `always`, which is a different case than the one under discussion.
> Currently it is the offset to the start of the second token of the
> parent line.
No. This indentation is the one you get when we use the *other* rule
which tries to indent depending on the structure of the code on the
line. E.g. you get that when `sh-indent-after-continuation` is nil.
> Kevin wants to change it, so that it would be the start
> of the first token of the parent non-continuation line +
> sh-basic-offset.
We're miscommunicating, then.
Those who want that just need
(setq sh-indent-after-continuation 'always)
AFAIK this thread is about fixing the indentation from
$(catfood)/foo bar \
baz
to
$(catfood)/foo bar \
baz
[ and AFAIK it's a plain bug-fix, not a change in style. ]
Stefan
next prev parent reply other threads:[~2021-09-06 14:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 10:49 Debugging SMIE for sh-script.el Kévin Le Gouguec
2021-09-02 12:07 ` Nikolay Kudryavtsev
2021-09-02 17:19 ` Kévin Le Gouguec
2021-09-02 18:09 ` Nikolay Kudryavtsev
2021-09-02 20:29 ` Kévin Le Gouguec
2021-09-02 19:50 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-09-02 21:37 ` Kévin Le Gouguec
2021-09-02 23:54 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-09-03 7:09 ` Kévin Le Gouguec
2021-09-03 12:12 ` Stefan Monnier
2021-09-05 15:48 ` Nikolay Kudryavtsev
2021-09-05 16:27 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-09-05 16:41 ` Nikolay Kudryavtsev
2021-09-05 17:23 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-09-05 18:01 ` Nikolay Kudryavtsev
2021-09-05 23:02 ` Stefan Monnier
2021-09-06 12:47 ` Nikolay Kudryavtsev
2021-09-06 14:01 ` Stefan Monnier [this message]
2021-09-06 17:24 ` Nikolay Kudryavtsev
2021-09-06 20:23 ` Stefan Monnier
2021-09-12 17:40 ` Kévin Le Gouguec
2021-09-02 19:47 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-09-02 20:39 ` Kévin Le Gouguec
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=jwva6kp959g.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@gnu.org \
--cc=nikolay.kudryavtsev@gmail.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.
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).