From: Stefan Kangas <stefan@marxist.se>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: occitan@esperanto.org, Carlos Pita <carlosjosepita@gmail.com>,
18380-done@debbugs.gnu.org
Subject: bug#18380: 24.3.93; sh-script multiline quoted subshell wreaks havoc with indentation
Date: Mon, 30 Sep 2019 04:54:33 +0200 [thread overview]
Message-ID: <CADwFkmmJUzJ325X+kVJJb3MDuuABwkQaLB84eMBSuy80PMzEiA@mail.gmail.com> (raw)
In-Reply-To: <877g1n1kjf.fsf@gmail.com>
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> This will see the { as quoted:
>> "$(echo "{")"
>>
>> while this will not:
>>
>> "$(echo
>> "{")"
>
> Actually, it depends: sometimes it will sometimes it won't :-(
>
>> after this line indentation is broken as Emacs thinks there is an
>> unclosed open brace.
>>
>> The problem with multiline quoted subshells is more general, as
>> remarked by this comment in sh-script.el:
>>
>> ;; FIXME: This can (and often does) match multiple lines, yet it makes no
>> ;; effort to handle multiline cases correctly, so it ends up being
>> ;; rather flaky.
>
> Indeed, the problem you show is the direct result of the problem alluded
> to in the above comment. I installed the patch below which seems to help.
I can't reproduce the original problem on current master.
Since there also has been no further updates here in 5 years, I'm going
to close this bug report. If any of this is still an issue, please
reopen the bug report.
Best regards,
Stefan Kangas
prev parent reply other threads:[~2019-09-30 2:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 14:29 bug#18380: 24.3.93; sh-script multiline quoted subshell wreaks havoc with indentation Carlos Pita
2014-09-03 0:39 ` Stefan Monnier
2019-09-30 2:54 ` Stefan Kangas [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmmJUzJ325X+kVJJb3MDuuABwkQaLB84eMBSuy80PMzEiA@mail.gmail.com \
--to=stefan@marxist.se \
--cc=18380-done@debbugs.gnu.org \
--cc=carlosjosepita@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=occitan@esperanto.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.