unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Debugging SMIE for sh-script.el
Date: Thu, 02 Sep 2021 19:19:29 +0200	[thread overview]
Message-ID: <87tuj26gke.fsf@gmail.com> (raw)
In-Reply-To: <04ae9f30-5e65-d7de-501e-92d557ddf84c@gmail.com> (Nikolay Kudryavtsev's message of "Thu, 2 Sep 2021 15:07:11 +0300")

Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com> writes:

> SMIE funcalls smie-indent-functions until one of them returns
> non-nil. If we do smie-config-show-intent on your line we get:
>
> Rules used: :list-intro "" -> nil
>
> This means that our line has been indented by the default logic of
> smie-indent-exps. If we go through it we'll see that it's trying to
> align with the first arg of sexp which it thinks is "/bar". So in
> effect it's treating your expression as if it was:
>
> ({foo} /bar
>
>            --baz \ --quux)

Thanks, smie-config-show-intent looks like a neat debugging tool, I'm
sure it will help me understand how to achieve what I want (cf. commit
6392bc37a, which was reverted because of bug#50320).


I'm still at a loss regarding why this snippet returns 6, despite
sh-smie--indent-continuation returning nil:

#+begin_src elisp
(let ((sh-indent-after-continuation nil))
  (smie-indent-calculate))
#+end_src

This is not necessarily an SMIE-related issue; it feels like there is
something more fundamental I don't understand about what's going on.
This specific question is what prompted my message to help-gnu-emacs.



  reply	other threads:[~2021-09-02 17:19 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 [this message]
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
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=87tuj26gke.fsf@gmail.com \
    --to=kevin.legouguec@gmail.com \
    --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).